Filter Coefficient Configuration in New Radio Systems

ABSTRACT

Aspects of filtering coefficient configuration operations are described. Some aspects include a user equipment (UE) decoding a measurement configuration information element (IE) including a measurement quantity parameter, a reference signal (RS)-type filter configuration and at least one filter coefficient. In some aspects, the UE filters at least one of a cell measurement result and a beam measurement result, according to the measurement configuration IE. If the measurement quantity parameter indicates the cell measurement quantity, the UE can filter the cell measurement result according to the RS type filter configuration and the filter coefficient to determine a measurement evaluation input for a measurement reporting operation. If the measurement quantity parameter indicates the beam measurement quantity, the UE can filter the beam measurement result according to the RS type filter configuration and the filter coefficient to determine a beam measurement selection input for a beam measurement selection operation.

PRIORITY CLAIM

This application is a continuation of U.S. patent application Ser. No.16/162,541, filed Oct. 17, 2018, which claims priority to U.S.Provisional Patent Application Ser. No. 62/575,281 filed Oct. 20, 2017,each of which is incorporated herein by reference in its entirety.

TECHNICAL FIELD

Aspects pertain to wireless communications. Some aspects relate towireless networks including 3GPP (Third Generation Partnership Project)networks, 3GPP LTE (Long Term Evolution) networks, 3GPP LTE-A (LTEAdvanced) networks, wireless local area networks (WLANs),fifth-generation (5G) networks including 5G new radio (NR) networks,next-generation (NG) networks, 5G-LTE networks, and software-definednetworks (SDNs).

BACKGROUND

In New Radio (NR) systems, signal measurement filtering can be used forradio resource management (RRM). One difference between NR and Long TermEvolution (LTE) systems is that NR includes beam level measurements andcell quality evaluation from beams. As a result, additional filterssignal measurement filtering can be used for beam reporting purposes.Filtering coefficient configurations and signalling methods are neededfor cell level measurements and beam level measurements.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates a diagram of measurement and filtering system, inaccordance with some aspects;

FIG. 2A illustrates an exemplary architecture of a network in accordancewith some aspects;

FIG. 2B is a simplified diagram of an exemplary Next-Generation (NG)system architecture in accordance with some aspects;

FIG. 2C illustrates an example MulteFire Neutral Host Network (NHN) 5Garchitecture in accordance with some aspects;

FIG. 2D illustrates an exemplary functional split between nextgeneration radio access network (NG-RAN) and the 5G Core network (5GC)in accordance with some aspects;

FIG. 2E illustrates an exemplary non-roaming 5G system architecture inaccordance with some aspects;

FIG. 2F illustrates an exemplary non-roaming 5G system architecture inaccordance with some aspects;

FIG. 2G illustrates an example Cellular Internet-of-Things (CIoT)network architecture in accordance with some aspects;

FIG. 2H illustrates an example Service Capability Exposure Function(SCEF) in accordance with some aspects;

FIG. 2I illustrates an example roaming architecture for SCEF inaccordance with some aspects;

FIG. 2J illustrates components of an exemplary NG Radio Access Network(RAN) architecture, in accordance with some aspects;

FIG. 3A is a block diagram of an exemplary SDN architecture, inaccordance with some aspects;

FIG. 3B is a block diagram of an exemplary SDN architecture, inaccordance with some aspects;

FIG. 3C is a block diagram illustrating components, according to someexample aspects, of a system to support network function virtualization;

FIG. 4 is an illustration of an exemplary user plane protocol stack inaccordance with some aspects;

FIG. 5 illustrates example components of a device in accordance withsome aspects;

FIG. 6 illustrates example interfaces of baseband circuitry inaccordance with some aspects;

FIG. 7 is an illustration of an exemplary control plane protocol stackin accordance with some aspects;

FIG. 8 is an illustration of an exemplary user plane protocol stack inaccordance with some aspects;

FIG. 9 is a block diagram illustrating components, according to someexample aspects, able to read instructions from a machine-readable orcomputer-readable medium (e.g., a non-transitory machine-readablestorage medium) and perform any one or more of the methodologiesdiscussed herein;

FIG. 10 illustrates a block diagram of an example computing machine, inaccordance with some aspects; and

FIG. 11 illustrates generally a flow of an exemplary method ofconfiguring filter coefficients, in accordance with some aspects.

FIG. 12 illustrates generally a flow of an exemplary method ofconfiguring filtering coefficients, in accordance with some aspects.

DETAILED DESCRIPTION

The following description and the drawings sufficiently illustrateaspects to enable those skilled in the art to practice them. Otheraspects may incorporate structural, logical, electrical, process, andother changes. Portions and features of some aspects may be included in,or substituted for, those of other aspects. Aspects set forth in theclaims encompass all available equivalents of those claims.

Radio resource management (RRM) configuration can include measurementsthat are performed by user equipment (UE). Such measurements can includeintra-frequency NR measurements, inter-frequency NR measurements orinter-radio access technology (RAT) measurements for Evolved UniversalMobile Telecommunications System (UMTS) Terrestrial Radio Access(E-UTRA). Measurements can be beam level measurements or cell levelmeasurements. In some aspects, a network entity can configure ameasurement type to be performed, such as an access point (AP), radioaccess network (RAN) node or base station (BS) described in furtherdetail with respect to FIGS. 2A and 2B. Configuring the measurement typecan include encoding, and transmitting within signalling to a UE (e.g.,UE 201 or 203 of FIGS. 2A or 2B), a measurement configuration. In anon-limiting example, a measurement configuration can define a frequencyof measurement, a signal type for measurement and a location withintime-frequency resources that a UE is to measure.

A measurement configuration can define one or several reportingconfigurations, and a reporting configuration can define reportingcriteria, for example, criteria by which a UE decides whether togenerate a measurement report and criteria by which the network decideswhether to handover the UE from one cell to another cell (e.g.,reporting events). In some aspects, reporting criteria can include eventtriggered reporting, periodic reporting and event triggered periodicreporting. In some aspects, the measurement configuration can includefilter coefficients and the UE may use the filter coefficients to filtermeasurements for evaluating reporting criteria and for determiningmeasurements to report. Certain filtering coefficients are specific tothe RRC protocol layer, and the UE can receive such filter coefficientswithin RRC signalling from a network entity (e.g., AP, BS, RAN node) andapply the coefficients in filtering operations on measurements. Aspectsherein describe, in part, measurement configurations and specificallyconfigurations of filter coefficients.

FIG. 1 illustrates a diagram of measurement and filtering system, inaccordance with some aspects. Operations represented in the measurementand filtering system 100, or portions of the operations represented, maybe performed by any one or more of the network entities or devicesdescribed herein. For example, the network entities or devices,including network function virtualization (NFV)-based orsoftware-defined networking (SDN)-based network entities or devices ofFIGS. 2A-2J.

In some aspects, the measurement and filtering system 100 can includefiltering operations that can involve multiple protocol layers (e.g.,layers of a protocol functions of the protocol layers) in a networksystem. Filtering operations, for example, can be performed in a layer 1protocol layer (e.g., physical layer) or in a layer 3 protocol layer(e.g., radio resource control (RRC) layer), or both layer 1 and layer 3of the network system. Details of such protocol layers are furtherdescribed with respect to FIGS. 4, 7 and 8. The measurement andfiltering system 100 can include operations such as beam measurement115, physical layer filtering 104 (e.g., layer 1 filtering), beamconsolidation and/or selection 105, RRC layer filtering for cell quality107, evaluation of reporting criteria 109, RRC layer filtering of beammeasurements 111 and beam selection for measurement reporting 113.

A device (e.g., UE 201 or 203) can measure one or multiple receivedbeams, such as beams transmitted from an AP (e.g., RAN node 213, 215,243) in the network (e.g., system 200A, 200B), for example, processingcircuitry within an apparatus of the UE can configure transceivercircuitry to receive such beams. According to the UE implementation 103can filter the beam measurements. In certain aspects, a filter (e.g.,layer 1 filter or layer 3 filter) can be configured to perform filteringof beam measurements and/or cell measurements. The filter can beincluded, for example, within an apparatus and/or circuitry of the UE,and in some instances can be a virtualized or software defined filterfunction.

In some aspects, the device can filter the beam measurements accordingto a UE-specific implementation in layer 1 (e.g., physical layer). As aresult of filtering the beam measurements, the UE can generate beamspecific measurements 117 that can be reported by the physical layer tothe RRC layer after the physical layer filtering. Using the beamspecific measurements 117 as inputs, the UE can consolidate beamspecific measurements 105 to derive a cell quality value 119. In someaspects, beam consolidation and/or beam selection can be configured andcontrolled by the AP through RRC signalling transmitted from the AP tothe UE.

In some aspects, the RRC signalling can also include a configuration ofRRC layer (e.g., layer 3) filtering parameters and/or filteringcoefficients. The UE can use the filtering parameters and coefficientsto filter the measurements, for example, using RRC layer filtering. Insome aspects, using the cell quality value 119 as an input, the UE canuse RRC layer filtering for cell quality 107. As a result of filteringfor cell quality 107, the UE can generate input values 121 forevaluation of reporting criteria. In certain aspects, one or moreadditional inputs 123 may be used for the evaluation of reportingcriteria.

The evaluation of reporting criteria 109 can include evaluating whethermeasurement reporting is to be used to report measurements to a networkentity (e.g., AP, RAN node). A reporting event can be an event where asignal strength of a neighbor cell becomes an offset better than asignal strength of a primary cell (PCell) (e.g., A3 event) or where thesignal strength of the neighbor cell becomes an offset better than thesignal strength of a secondary cell (SCell) (e.g., A6 event). In someaspects, reported measurements can include information to be used forRRM, reference signal received power (RSRP), reference signal receivedquality (RSRQ), and/or signal-to-interference-plus-noise ratio (SINR).The evaluation can be based on more than one flow of measurements orinputs 121, for example, for the purpose of comparing between differentmeasurements (e.g., 121 and 123). In some aspects, the UE can evaluatethe reporting criteria every time a new measurement result is reportedat inputs 121 and 123. Reporting criteria can be configured through RRCsignalling (e.g., transmitted by an AP, BS or RAN node to a UE).

In some aspects, the UE or a filter within the UE can perform RRC layer(e.g., layer 3) beam filtering 111 on measurements, such as thebeam-specific measurements 117. Beam filtering can be configured by RRCsignalling that can include filtering parameters and/or filteringcoefficients, of which the UE can use for filtering beam-specificmeasurements 117. As a result of the beam filtering 111, the UE cangenerate a filtered beam-specific measurement 127 that can be used as aninput for selecting a number of measurements 113 to be evaluated andpotentially reported in a measurement report. In certain aspects, thebeam-specific measurements 117 and the filtered beam-specificmeasurement 127 can be a number of beams (e.g., K beams) that cancorrespond to measurements in certain time-frequency resources. Forexample, time-frequency resources, such as synchronization signal blocks(SSB) (e.g., NR-SS block) or channel state information-reference signals(CSI-RS). Such resources can be configured by a network entity (e.g.,BS, RAN node) through the RRC layer and detected by the UE through thephysical layer.

The UE can perform beam selection for beam reporting, in some aspects,and the UE can select a number of measurements from the filteredbeam-specific measurements 127. The selected filtered beam-specificmeasurements 127 can be used for measurement reporting 129 (e.g., Xbeams) and the selecting can be configured through RRC signalling. Ameasurement report, including cell measurement quantities and beammeasurement quantities that are filtered according to filtercoefficients, can be encoded by processing circuitry of the UE andtransmitted by transceiver circuitry to the AP, BS or RAN node. In someaspects, the measurement configuration in RRC signalling can include oneor more parameters, information elements (IE) and/or coefficients, suchas a measurement object, a reporting configuration, a measurementidentity, and a quantity configuration.

The measurement object parameter can include information such as a listof objects on which the UE shall perform measurements. For example, ameasurement object can include a list of measurement objects to add,remove and/or to modify. In certain aspects, the UE can store in memorythe list of measurement objects and add, remove or modify the listaccording to the measurement object parameters or coefficients in theRRC signalling. In some aspects, the RRC signalling can includedifferent parameters or coefficients to indicate different measurementobjects (e.g., two measurement objects are indicated by separatecoefficients), and in other aspects, the same coefficient can indicatemore than one measurement object.

In some aspects, the reporting configuration parameter can include alist of reporting configurations and a single measurement object cancorrespond to one or multiple reporting configurations. A reportingconfiguration can consist of a reporting criterion that triggers the UEto send a measurement report that can be a periodical or a single eventdescription. The reporting configuration can also include a referencesignal (RS) type indication that the UE can use for beam and cellmeasurement results (e.g., SSB or CSI-RS measurement results). Thereporting configuration can also include a reporting format includingthe quantities per cell and per beam, and other associated informationsuch as the maximum number of cells and the maximum number beams percell, that the UE can include in a measurement report.

In some aspects, a measurement identity parameter can include a list ofmeasurement identities where a measurement identity can link onemeasurement object with one reporting configuration. By configuringmultiple measurement identities, more than one measurement object can belinked to the same reporting configuration, and more than one reportingconfiguration can be linked to the same measurement object. In certainaspects, the measurement identity is also included in the measurementreport that triggers the reporting, serving as a reference to thenetwork. In some aspects, a quantity configuration parameter can definea measurement filtering configuration that can be used for all eventevaluation and related reporting, and for periodical reporting of themeasurement. In some aspects, the quantity configuration parameter(e.g., IE) can specify measurement quantities and RRC layer (e.g., layer3) filtering coefficients, for example, for NR measurements and E-UTRAmeasurements.

The quantity configuration IE, for example, can include one or moreparameters and/or coefficients (e.g., layer 3 filtering coefficients)for the UE to use in filtering cell and beam measurements. Suchparameters (e.g., coefficients) can include, for example, separatecoefficients for cell quantity and beam quantity, separate coefficientsfor reference signal types such as a synchronization signal block(SSB)-based coefficient or a channel state information-reference signal(CSI-RS)-based coefficient, and separate filter coefficients (e.g.,layer 3 filtering coefficients) such as a reference signal receivedpower (RSRP) filter coefficient, a reference signal received quality(RSRQ) filter coefficient and a reference signal-signal to interferenceplus noise ratio (RS-SINR) filter coefficient. In some aspects, the UEcan use the measurement configuration (e.g., received in RRCsignalling), and any of the parameters or coefficients included therein,to perform beam and cell measurements and measurement reporting, asdescribed further below with respect to FIG. 11.

FIG. 2A illustrates an architecture of a system 200A of a network inaccordance with some aspects. In some aspects, the system 200A may beconfigured for the measurement and filtering operations and/or filteringcoefficient signalling methods described herein. The system 200A isshown to include a user equipment (UE) 201 and a UE 201/203. The UEs201/203 may be smartphones (e.g., handheld touchscreen mobile computingdevices connectable to one or more cellular networks) or any mobile ornon-mobile computing device, such as Personal Data Assistants (PDAs),pagers, laptop computers, desktop computers, wireless handsets, or anycomputing device including a wireless communications interface. In someaspects, the UE 201/203 may be Internet-of-Things (IoT)-enabled devices,configured to communicate with a RAN 210 or a core network (CN) 221,including but not limited to vehicles or drones.

In some aspects, any of the UEs 201/203 can comprise an Internet ofThings (IoT) UE, which can comprise a network access layer designed forlow-power IoT applications utilizing short-lived UE connections. An IoTUE can utilize technologies such as machine-to-machine (M2M) ormachine-type communications (MTC) for exchanging data with an MTC serveror device via a public land mobile network (PLMN), Proximity-BasedService (ProSe) or device-to-device (D2D) communication, sensornetworks, or IoT networks. The M2M or MTC exchange of data may be amachine-initiated exchange of data. An IoT network describesinterconnecting IoT UEs, which may include uniquely identifiableembedded computing devices (within the Internet infrastructure), withshort-lived connections. The IoT UEs may execute background applications(e.g., keep-alive messages, status updates, etc.) to facilitate theconnections of the IoT network.

The UEs 201/203 may be configured to connect, in a wired or wirelessconfiguration, e.g., communicatively couple, with a radio access network(RAN) 210. The RAN 210 may be, for example, an Evolved Universal MobileTelecommunications System (UMTS) Terrestrial Radio Access Network(E-UTRAN), a NextGen RAN (NG-RAN), 5G RAN, or some other type of RAN.The UEs 201/203 utilize connections 205, each of which comprises aphysical communications interface or layer (discussed in further detailbelow); in this example, the connections 205 are illustrated as an airinterface to enable communicative coupling, and can be consistent withcellular communications protocols, such as a Global System for MobileCommunications (GSM) protocol, a code-division multiple access (CDMA)network protocol, a Push-to-Talk (PTT) protocol, a PTT over Cellular(POC) protocol, a Universal Mobile Telecommunications System (UMTS)protocol, a 3GPP Long Term Evolution (LTE) protocol, a fifth generation(5G) protocol, a New Radio (NR) protocol, and the like.

In this aspect, the UEs 201/203 may further directly exchangecommunication data via a ProSe interface 207. The ProSe interface 207may alternatively be referred to as a sidelink interface comprising oneor more logical channels, including but not limited to a PhysicalSidelink Control Channel (PSCCH), a Physical Sidelink Shared Channel(PSSCH), a Physical Sidelink Discovery Channel (PSDCH), and a PhysicalSidelink Broadcast Channel (PSBCH). The UE 201/203 is shown to beconfigured to access an access point (AP) 211 via connection 209. Theconnection 209 can comprise a local wireless connection, such as aconnection consistent with any IEEE 802.11 protocol, where the AP 211would comprise a wireless fidelity (WiFi®) router. In this example, theAP 211 is shown to be connected to the Internet without connecting tothe core network of the wireless system (described in further detailbelow).

The RAN 210 can include one or more access nodes (ANs) or access points(APs) that enable the connections 205, for example, for filtercoefficient configuration and measurement operations. These ANs can bereferred to as base stations (BSs), NodeBs, evolved NodeBs (eNBs), nextGeneration NodeBs (e.g., gNB, ng-eNB), RAN nodes, and so forth, and cancomprise ground stations (e.g., terrestrial access points) or satellitestations providing coverage within a geographic area (e.g., a cell). Insome aspects, the communication nodes 213 and 215 can betransmission/reception points (TRPs). In instances when thecommunication nodes 213 and 215 are NodeBs (e.g., eNBs or gNBs), one ormore TRPs can function within the communication cell of the NodeBs. Insome aspects, a NodeB can be a E-UTRA-NR (EN)-gNB (en-gNB) configured tosupport E-UTRA-NR Dual Connectivity (EN-DC) (e.g., multi-RAT DualConnectivity (MR-DC)), in which a UE may be connected to one eNB thatacts as a master node (MN) and one en-gNB that acts as a secondary node(SN).

The RAN 210 may include one or more RAN nodes for providing macrocells,e.g., macro RAN node 213, and one or more RAN nodes for providingfemtocells or picocells (e.g., cells having smaller coverage areas,smaller user capacity, or higher bandwidth compared to macrocells),e.g., low power (LP) RAN node 215. Any of the RAN nodes 213 and 215 canterminate the air interface protocol and can be the first point ofcontact for the UEs 201/203. In some aspects, any of the RAN nodes 213and 215 can fulfill various logical functions for the RAN 210 including,but not limited to, radio network controller (RNC) functions such asradio bearer management, uplink and downlink dynamic radio resourcemanagement and data packet scheduling, and mobility management. In anexample, any of the nodes 213 or 215 can be a new generation node-B(gNB), an evolved node-B (eNB), or another type of RAN node.

In accordance with some aspects, the UEs 201/203 can be configured tocommunicate using Orthogonal Frequency-Division Multiplexing (OFDM)communication signals with each other or with any of the RAN nodes 213and 215 over a multicarrier communication channel in accordance variouscommunication techniques, such as, but not limited to, an OrthogonalFrequency-Division Multiple Access (OFDMA) communication technique(e.g., for downlink communications) or a Single Carrier FrequencyDivision Multiple Access (SC-FDMA) communication technique (e.g., foruplink and ProSe or sidelink communications), although the scope of theaspects is not limited in this respect. The OFDM signals can comprise aplurality of orthogonal subcarriers.

In some aspects, a downlink resource grid can be used for downlinktransmissions from any of the RAN nodes 213 and 215 to the UEs 201/203,while uplink transmissions can utilize similar techniques. The grid canbe a time-frequency grid, called a resource grid or time-frequencyresource grid, which is the physical resource in the downlink in eachslot. Such a time-frequency plane representation is a common practicefor OFDM systems, which makes it intuitive for radio resourceallocation. Each column and each row of the resource grid corresponds toone OFDM symbol and one OFDM subcarrier, respectively. The duration ofthe resource grid in the time domain corresponds to one slot in a radioframe. The smallest time-frequency unit in a resource grid is denoted asa resource element. Each resource grid may comprise a number of resourceblocks, which describe the mapping of certain physical channels toresource elements. Each resource block comprises a collection ofresource elements; in the frequency domain, this may represent thesmallest quantity of resources that currently can be allocated. Thereare several different physical downlink channels that are conveyed usingsuch resource blocks.

The physical downlink shared channel (PDSCH) may carry user data andhigher-layer signalling to the UEs 201/203. The physical downlinkcontrol channel (PDCCH) may carry information about the transport formatand resource allocations related to the PDSCH channel, among otherthings. It may also inform the UEs 201/203 about the transport format,resource allocation, and H-ARQ (Hybrid Automatic Repeat Request)information related to the uplink shared channel. Typically, downlinkscheduling (assigning control and shared channel resource blocks to theUE 102 within a cell) may be performed at any of the RAN nodes 213 and215 based on channel quality information fed back from any of the UEs201/203. The downlink resource assignment information may be sent on thePDCCH used for (e.g., assigned to) each of the UEs 201/203.

The PDCCH may use control channel elements (CCEs) to convey the controlinformation. Before being mapped to resource elements, the PDCCHcomplex-valued symbols may first be organized into quadruplets, whichmay then be permuted using a sub-block interleaver for rate matching.Each PDCCH may be transmitted using one or more of these CCEs, whereeach CCE may correspond to nine sets of four physical resource elementsknown as resource element groups (REGs). Four Quadrature Phase ShiftKeying (QPSK) symbols may be mapped to each REG. The PDCCH can betransmitted using one or more CCEs, depending on the size of thedownlink control information (DCI) and the channel condition. There canbe four or more different PDCCH formats defined in LTE with differentnumbers of CCEs (e.g., aggregation level, L=1, 2, 4, or 8).

Some aspects may use concepts for resource allocation for controlchannel information that are an extension of the above-describedconcepts. For example, some aspects may utilize an enhanced physicaldownlink control channel (EPDCCH) that uses PDSCH resources for controlinformation transmission. The EPDCCH may be transmitted using one ormore enhanced control channel elements (ECCEs). Similar to above, eachECCE may correspond to nine sets of four physical resource elementsknown as an enhanced resource element groups (EREGs). An ECCE may haveother numbers of EREGs in some situations.

Entities within a RAN (e.g., RAN 210), such as RAN Nodes (e.g., 213,215), can be connected (e.g., communicatively coupled), in a wired orwireless configuration, to one or more network entities, including toone another. For example, a connection can include a backhaulconnection. Wired connections can include ethernet, coaxial cable, fiberoptic cable, although aspects are not so limited. The RAN 210 is shownto be communicatively coupled to a core network (CN) 221 via an S1interface 217. In aspects, the CN 221 may be an evolved packet core(EPC) network, a NextGen Packet Core (NPC) network, or some other typeof CN (e.g., as illustrated in reference to FIGS. 2B-2I). In this aspectthe S1 interface 217 is split into two parts: the S1-U interface 214,which carries traffic data between the RAN nodes 213 and 215 and theserving gateway (S-GW) 231, and the S1-mobility management entity (MME)interface 219, which is a signalling interface between the RAN nodes 213and 215 and MMEs 223.

In this aspect, the CN 221 comprises the MMEs 223, the S-GW 231, thePacket Data Network (PDN) Gateway (P-GW) 223, and a home subscriberserver (HSS) 225. The MMEs 223 may be similar in function to the controlplane of legacy Serving General Packet Radio Service (GPRS) SupportNodes (SGSN). The MMEs 223 may manage mobility aspects in access such asgateway selection and tracking area list management. The HSS 225 maycomprise a database for network users, including subscription-relatedinformation to support the network entities' handling of communicationsessions. The CN 221 may comprise one or several HSSs 225, depending onthe number of mobile subscribers, on the capacity of the equipment, onthe organization of the network, etc. For example, the HSS 225 canprovide support for routing/roaming, authentication, authorization,naming/addressing resolution, location dependencies, etc.

The S-GW 231 may terminate the S1 interface 219 towards the RAN 210, androute data packets between the RAN 210 and the CN 221. In addition, theS-GW 231 may be a local mobility anchor point for inter-RAN nodehandovers and also may provide an anchor for inter-3GPP mobility. Otherresponsibilities may include lawful intercept, charging, and some policyenforcement. The P-GW 233 may terminate an SGi interface toward a PDN.The P-GW 233 may route data packets between the CN 221 and externalnetworks such as a network including the application server 237(alternatively referred to as application function (AF)) via an InternetProtocol (IP) interface 227. The P-GW 233 can also communicate data toother external networks 235, which can include the Internet, IPmultimedia subsystem (IPS) network, and other networks. Generally, theapplication server 237 may be an element offering applications that useIP bearer resources with the core network (e.g., UMTS Packet Services(PS) domain, LTE PS data services, etc.). In this aspect, the P-GW 233is shown to be communicatively coupled to an application server 237 viaan IP communications interface 227. The application server 237 can alsobe configured to support one or more communication services (e.g.,Voice-over-Internet Protocol (VoIP) sessions, PTT sessions, groupcommunication sessions, social networking services, etc.) for the UEs201/203 via the CN 221.

The P-GW 233 may further be a node for policy enforcement and chargingdata collection. Policy and Charging Enforcement Function (PCRF) 229 isthe policy and charging control element of the CN 221. In a non-roamingscenario, there may be a single PCRF in the Home Public Land MobileNetwork (HPLMN) associated with a UE's Internet Protocol ConnectivityAccess Network (IP-CAN) session. In a roaming scenario with localbreakout of traffic, there may be two PCRFs associated with a UE'sIP-CAN session: a Home PCRF (H-PCRF) within a HPLMN and a Visited PCRF(V-PCRF) within a Visited Public Land Mobile Network (VPLMN). The PCRF229 may be communicatively coupled to the application server 237 via theP-GW 233. The application server 237 may signal the PCRF 229 to indicatea new service flow and select the appropriate Quality of Service (QoS)and charging parameters. The PCRF 229 may provision this rule into aPolicy and Charging Enforcement Function (PCEF) (not shown) with theappropriate traffic flow template (TFT) and QoS class of identifier(QCI), which commences the QoS and charging as specified by theapplication server 237.

In an example, any of the nodes 213 or 215 can be configured tocommunicate to the UEs 201/203 (e.g., dynamically) by an antenna panelselection and a receive (Rx) beam selection that can be used by the UEfor data reception on a physical downlink shared channel (PDSCH) as wellas for channel state information reference signal (CSI-RS) measurementsand channel state information (CSI) calculation. In an example, any ofthe nodes 213 or 215 can be configured to communicate to the UEs 201/203(e.g., dynamically) by an antenna panel selection and a transmit (Tx)beam selection that can be used by the UE for data transmission on aphysical uplink shared channel (PUSCH) as well as for sounding referencesignal (SRS) transmission.

In some aspects, the communication network 240A can be an IoT network.One of the current enablers of IoT is the narrowband-IoT (NB-IoT).NB-IoT has objectives such as coverage extension, UE complexityreduction, long battery lifetime, and backward compatibility with theLTE network. In addition, NB-IoT aims to offer deployment flexibilityallowing an operator to introduce NB-IoT using a small portion of itsexisting available spectrum, and operate in one of the following threemodalities: (a) standalone deployment (the network operates in re-farmedGSM spectrum); (b) in-band deployment (the network operates within theLTE channel); and (c) guard-band deployment (the network operates in theguard band of legacy LTE channels). In some aspects, such as withfurther enhanced NB-IoT (FeNB-IoT), support for NB-IoT in small cellscan be provided (e.g., in microcell, picocell or femtocell deployments).One of the challenges NB-IoT systems face for small cell support is theUL/DL link imbalance, where for small cells the base stations have lowerpower available compared to macro-cells, and, consequently, the DLcoverage can be affected or reduced. In addition, some NB-IoT UEs can beconfigured to transmit at maximum power if repetitions are used for ULtransmission. This may result in large inter-cell interference in densesmall cell deployments.

FIG. 2B illustrates an exemplary Next Generation (NG) systemarchitecture 200B in accordance with some aspects. Referring to FIG. 2B,the NG system architecture 200B includes NG-RAN 239 and a 5G networkcore (5GC) 241. The NG-RAN 239 can include a plurality of nodes, forexample, gNBs 243A and 243B, and NG-eNBs 245A and 245B. System 200B caninclude wired or wireless connections (e.g., communicative coupling) towired or wireless communication devices, such as client devices. ThegNBs 243A/243B and the NG-eNBs 245A/245B can be communicatively coupledto the UE 201/203 via, for example, an N1 interface. The core network241 (e.g., a 5G core network or 5GC) can include an access and mobilitymanagement function (AMF) 247 or a user plane function (UPF) 249. TheAMF 247 and the UPF 249 can be communicatively coupled to the gNBs243A/243B and the NG-eNBs 245A/245B via NG interfaces. Morespecifically, in some aspects, the gNBs 243A/243B and the NG-eNBs245A/245B can be connected to the AMF 247 by NG-C interfaces, and to theUPF 249 by NG-U interfaces. The gNBs 243A/243B and the NG-eNBs 245A/245Bcan be coupled to each other via Xn interfaces.

In some aspects, a gNB 243 can include a node providing New Radio (NR)user plane and control plane protocol termination towards the UE, andcan be connected via the NG interface to the 5GC 241. In some aspects,an NG-eNB 245A/245B can include a node providing evolved universalterrestrial radio access (E-UTRA) user plane and control plane protocolterminations towards the UE, and is connected via the NG interface tothe 5GC 241. In some aspects, any of the gNBs 243A/243B and the NG-eNBs245A/245B can be implemented as a base station (BS), a mobile edgeserver, a small cell, a home eNB, although aspects are not so limited.

FIG. 2C illustrates an example MulteFire Neutral Host Network (NHN) 5Garchitecture 200C in accordance with some aspects. Referring to FIG. 2C,in some aspects, the MulteFire 5G architecture 200C can include awireless communication device, such as a UE (e.g., UE 201/203), a NG-RAN(e.g., NG-RAN 239 or similar) and a core network (e.g., core network 241or similar). The NG-RAN can be a MulteFire NG-RAN (MF NG-RAN) 253, andthe core network can be a MulteFire 5G neutral host network (NHN) 251.In some aspects, the MF NHN 251 can include a neutral host AMF (NH AMF)255, a NH SMF 259, a NH UPF 257, and a local Authentication,Authorization and Accounting (AAA) proxy 261. The AAA proxy 261 canprovide connection to a 3GPP AAA server 263 and a participating serviceprovider AAA (PSP AAA) server 265. The NH-UPF 257 can provide aconnection to a data network 267.

The MF NG-RAN 253 can provide similar functionalities as an NG-RANoperating under a 3GPP specification. The NH-AMF 255 can be configuredto provide similar functionality as an AMF in a 3GPP 5G core network(e.g., described further in reference to FIG. 2D). The NH-SMF 259 can beconfigured to provide similar functionality as a SMF in a 3GPP 5G corenetwork (e.g., described further in reference to FIG. 2D). The NH-UPF257 can be configured to provide similar functionality as a UPF in a3GPP 5G core network (e.g., described further in reference to FIG. 2D).

FIG. 2D illustrates a functional split between a NG-RAN (e.g., NG-RAN239) and a 5G Core (e.g., 5GC 241) in accordance with some aspects. FIG.2D illustrates some of the functionalities the gNBs 243A/243B and theNG-eNBs 245A/245B can perform within the NG-RAN 239, as well as the AMF247, the UPF 249, and a Session Management Function (SMF) 277 within the5GC 241. In some aspects, the 5GC 241 can provide access to the Internet269 to one or more devices via the NG-RAN 239.

In some aspects, the gNBs 243A/243B and the NG-eNBs 245A/245B can beconfigured to host the following functions: functions for Radio ResourceManagement (e.g., inter-cell radio resource management 271A, radiobearer control 271B, connection mobility control 271C, radio admissioncontrol 271D, dynamic allocation of resources to UEs in both uplink anddownlink (scheduling) 271F); IP header compression; encryption andintegrity protection of data; selection of an AMF at UE attachment whenno routing to an AMF can be determined from the information provided bythe UE; routing of User Plane data towards UPF(s); routing of ControlPlane information towards AMF; connection setup and release; schedulingand transmission of paging messages (originated from the AMF);scheduling and transmission of system broadcast information (originatedfrom the AMF or Operation and Maintenance); measurement and measurementreporting configuration for mobility and scheduling 271E; transportlevel packet marking in the uplink; session management; support ofnetwork slicing; QoS flow management and mapping to data radio bearers;support of UEs in RRC INACTIVE state; distribution function fornon-access stratum (NAS) messages; radio access network sharing; dualconnectivity; and tight interworking between NR and E-UTRA, to name afew.

In some aspects, the AMF 247 can be configured to host the followingfunctions, for example: NAS signalling termination; NAS signallingsecurity 279A; access stratum (AS) security control; inter core network(CN) node signalling for mobility between 3GPP access networks; idlestate/mode mobility handling 279B, including mobile device, such as a UEreachability (e.g., control and execution of paging retransmission);registration area management; support of intra-system and inter-systemmobility; access authentication; access authorization including check ofroaming rights; mobility management control (subscription and policies);support of network slicing; or SMF selection, among other functions.

The UPF 249 can be configured to host the following functions, forexample: mobility anchoring 275A (e.g., anchor point forIntra-/Inter-RAT mobility); packet data unit (PDU) handling 275B (e.g.,external PDU session point of interconnect to data network); packetrouting and forwarding; packet inspection and user plane part of policyrule enforcement; traffic usage reporting; uplink classifier to supportrouting traffic flows to a data network; branching point to supportmulti-homed PDU session; QoS handling for user plane, e.g., packetfiltering, gating, UL/DL rate enforcement; uplink traffic verification(SDF to QoS flow mapping); or downlink packet buffering and downlinkdata notification triggering, among other functions. The SessionManagement function (SMF) 277 can be configured to host the followingfunctions, for example: session management; UE IP address allocation andmanagement 279A; selection and control of user plane function (UPF); PDUsession control 279B, including configuring traffic steering at UPF 249to route traffic to proper destination; control part of policyenforcement and QoS; or downlink data notification, among otherfunctions.

FIG. 2E and FIG. 2F illustrate a non-roaming 5G system architecture inaccordance with some aspects. Referring to FIG. 2E, an exemplary 5Gsystem architecture 200E in a reference point representation isillustrated. More specifically, UE 201/203 can be in communication withRAN 281 as well as one or more other 5G core (5GC) network entities. The5G system architecture 200E includes a plurality of network functions(NFs), such as access and mobility management function (AMF) (e.g.,247), session management function (SMF) (e.g., 259), policy controlfunction (PCF) 283, application function (AF) 285, user plane function(UPF) (e.g., 249), network slice selection function (NSSF) 287,authentication server function (AUSF) 289, and unified data management(UDM)/home subscriber server (HSS) 291. The UPF 249 can provide aconnection to a data network (DN) (e.g., 267), which can include, forexample, operator services, Internet access, or third-party services.The AMF 247 can be used to manage access control and mobility and canalso include network slice selection functionality. The SMF 259 can beconfigured to set up and manage various sessions according to a networkpolicy. The UPF 249 can be deployed in one or more configurationsaccording to a desired service type. The PCF 283 can be configured toprovide a policy framework using network slicing, mobility management,and roaming (similar to PCRF in a 4G communication system). The UDM 291can be configured to store subscriber profiles and data (similar to anHSS in a 4G communication system).

In some aspects, the 5G system architecture 200E includes an IPmultimedia subsystem (IMS) 293 as well as a plurality of IP multimediacore network subsystem entities, such as call session control functions(CSCFs). More specifically, the IMS 293 includes a CSCF, which can actas a proxy CSCF (P-CSCF) 295 a serving CSCF (S-CSCF) 297, an emergencyCSCF (E-CSCF) (not illustrated in FIG. 2E), or interrogating CSCF(I-CSCF) 299. The P-CSCF 295 can be configured to be the first contactpoint for the UE 201/203 within the IM subsystem (IMS) 293. The S-CSCF297 can be configured to handle the session states in the network, andthe E-CSCF can be configured to handle certain aspects of emergencysessions such as routing an emergency request to the correct emergencycenter or public safety answering point (PSAP). The I-CSCF 299 can beconfigured to function as the contact point within an operator's networkfor all IMS connections destined to a subscriber of that networkoperator, or a roaming subscriber currently located within that networkoperator's service area. In some aspects, the I-CSCF 299 can beconnected to another IP multimedia network 298, (e.g. an IMS operated bya different network operator).

In some aspects, the UDM/HSS 291 can be coupled to an application server296, which can include a telephony application server (TAS) or anotherapplication server (AS). The AS 296 can be coupled to the IMS 293 viathe S-CSCF 297 or the I-CSCF 299. In some aspects, the 5G systemarchitecture 200E can use a unified access barring mechanism using oneor more of the techniques described herein, which access barringmechanism can be applicable for all RRC states of the UE 201/203, suchas RRC_IDLE, RRC_CONNECTED, and RRC_INACTIVE states.

In some aspects, the 5G system architecture 200E can be configured touse 5G access control mechanism techniques described herein, based onaccess categories that can be categorized by a minimum default set ofaccess categories, which are common across all networks. Thisfunctionality can allow the public land mobile network PLMN, such as avisited PLMN (VPLMN) to protect the network against different types ofregistration attempts, enable acceptable service for the roamingsubscriber and enable the VPLMN to control access attempts aiming atreceiving certain basic services. It also provides more options andflexibility to individual operators by providing a set of accesscategories, which can be configured and used in operator specific ways.

FIG. 2F illustrates an exemplary 5G system architecture 200F and aservice-based representation. System architecture 200F can besubstantially similar to (or the same as) system architecture 200E. Inaddition to the network entities illustrated in FIG. 2E, systemarchitecture 200F can also include a network exposure function (NEF) 294and a network repository function (NRF) 292. In some aspects, 5G systemarchitectures can be service-based and interaction between networkfunctions can be represented by corresponding point-to-point referencepoints Ni (as illustrated in FIG. 2E) or as service-based interfaces (asillustrated in FIG. 2F).

A reference point representation shows that an interaction can existbetween corresponding NF services. For example, FIG. 2E illustrates thefollowing reference points: N1 (between the UE 201/203 and the AMF 247),N2 (between the RAN 281 and the AMF 247), N3 (between the RAN 281 andthe UPF 249), N4 (between the SMF 259 and the UPF 249), N5 (between thePCF 283 and the AF 285), N6 (between the UPF 249 and the DN 252), N7(between the SMF 259 and the PCF 283), N8 (between the UDM 291 and theAMF 247), N9 (between two UPFs 249, additional UPF not shown), N10(between the UDM 291 and the SMF 259), N11 (between the AMF 247 and theSMF 259), N12 (between the AUSF 289 and the AMF 247), N13 (between theAUSF 289 and the UDM 291), N14 (between two AMFs 247, additional AMF notshown), N15 (between the PCF 283 and the AMF 247 in case of anon-roaming scenario, or between the PCF 283 and a visited network andAMF 247 in case of a roaming scenario, not shown), N16 (between twoSMFs; not illustrated in FIG. 2E), and N22 (between AMF 247 and NSSF287, not shown). Other reference point representations not shown in FIG.2E can also be used.

In some aspects, as illustrated in FIG. 2F, service-basedrepresentations can be used to represent network functions within thecontrol plane that enable other authorized network functions to accesstheir services. In this regard, 5G system architecture 200F can includethe following service-based interfaces: Namf 290A (a service-basedinterface exhibited by the AMF 247), Nsmf 290B (a service-basedinterface exhibited by the SMF 259), Nnef 290C (a service-basedinterface exhibited by the NEF 294), Npcf 290D (a service-basedinterface exhibited by the PCF 283), a Nudm 290E (a service-basedinterface exhibited by the UDM 291), Naf 290F (a service-based interfaceexhibited by the AF 285), Nnrf 290G (a service-based interface exhibitedby the NRF 292), Nnssf 290H (a service-based interface exhibited by theNSSF 287), Nausf 2901 (a service-based interface exhibited by the AUSF289). Other service-based interfaces (e.g., Nudr, N5g-eir, and Nudsf)not shown in FIG. 2F can also be used.

FIG. 2G illustrates an exemplary consumer IoT (CIoT) networkarchitecture in accordance with some aspects. Referring to FIG. 2G, theCIoT architecture 200G can include the UE 201/203 and the RAN 288coupled to a plurality of core network entities. In some aspects, the UE201/203 can be a machine-type communication (MTC) UE. The CIoT networkarchitecture 200G can further include a mobile services switching center(MSC) 286, MME 284, a serving GPRS support note (SGSN) 282, a S-GW 280,an IP-Short-Message-Gateway (IP-SM-GW) 278, a Short MessageService-Service Center (SMS-SC)/gateway mobile service center(GMSC)/Interworking MSC (IWMSC) 276, MTC interworking function (MTC-IWF)274, a Service Capability Exposure Function (SCEF) 272, a gateway GPRSsupport node (GGSN)/Packet-GW (P-GW) 270, a charging data function(CDF)/charging gateway function (CGF) 268, a home subscriber server(HSS)/a home location register (HLR) 277, short message entities (SME)266, MTC authorization, authentication, and accounting (MTC AAA) server264, a service capability server (SCS) 262, and application servers (AS)260 and 258. In some aspects, the SCEF 272 can be configured to securelyexpose services and capabilities provided by various 3GPP networkinterfaces. The SCEF 272 can also provide means for the discovery of theexposed services and capabilities, as well as access to networkcapabilities through various network application programming interfaces(e.g., API interfaces to the SCS 262).

FIG. 2G further illustrates various reference points between differentservers, functions, or communication nodes of the CIoT networkarchitecture 200G. Some example reference points related to MTC-IWF 274and SCEF 272 include the following: Tsms (a reference point used by anentity outside the 3GPP network to communicate with UEs used for MTC viaSMS), Tsp (a reference point used by a SCS to communicate with theMTC-IWF related control plane signalling), T4 (a reference point usedbetween MTC-IWF 274 and the SMS-SC 266 in the HPLMN), T6 a (a referencepoint used between SCEF 272 and serving MME 223), T6 b (a referencepoint used between SCEF 272 and serving SGSN 260), T8 (a reference pointused between the SCEF 272 and the SCS/AS 262/260), S6 m (a referencepoint used by MTC-IWF 274 to interrogate HSS/HLR 277), S6 n (a referencepoint used by MTC-AAA server 264 to interrogate HSS/HLR 277), and S6 t(a reference point used between SCEF 272 and HSS/HLR 277).

In some aspects, the CIoT UE 201/203 can be configured to communicatewith one or more entities within the CIoT architecture 200G via the RAN288 (e.g., CIoT RAN) according to a Non-Access Stratum (NAS) protocol,and using one or more reference points, such as a narrowband airinterface, for example, based on one or more communication technologies,such as Orthogonal Frequency-Division Multiplexing (OFDM) technology. Asused herein, the term “CIoT UE” refers to a UE capable of CIoToptimizations, as part of a CIoT communications architecture. In someaspects, the NAS protocol can support a set of NAS messages forcommunication between the CIoT UE 201/203 and an Evolved Packet System(EPS) Mobile Management Entity (MME) 284 and SGSN 282. In some aspects,the CIoT network architecture 200G can include a packet data network, anoperator network, or a cloud service network, having, for example, amongother things, a Service Capability Server (SCS) 280, an ApplicationServer (AS) 260, or one or more other external servers or networkcomponents.

The RAN 288 can be coupled to the HSS/HLR servers 277 and the AAAservers 264 using one or more reference points including, for example,an air interface based on an S6 a reference point, and configured toauthenticate/authorize CIoT UE 201/203 to access the CIoT network. TheRAN 288 can be coupled to the CIoT network architecture 200G using oneor more other reference points including, for example, an air interfacecorresponding to an SGi/Gi interface for 3GPP accesses. The RAN 288 canbe coupled to the SCEF 272 using, for example, an air interface based ona T6 a/T6 b reference point, for service capability exposure. In someaspects, the SCEF 272 may act as an API GW towards a third-partyapplication server such as AS 260. The SCEF 272 can be coupled to theHSS/HLR 277 and MTC AAA 264 servers using an S6 t reference point, andcan further expose an Application Programming Interface to networkcapabilities.

In certain examples, one or more of the CIoT devices disclosed herein,such as the CIoT UE 201/203, the CIoT RAN 288, etc., can include one ormore other non-CIoT devices, or non-CIoT devices acting as CIoT devices,or having functions of a CIoT device. For example, the CIoT UE 201/203can include a smart phone, a tablet computer, or one or more otherelectronic device acting as a CIoT device for a specific function, whilehaving other additional functionality. In some aspects, the RAN 288 caninclude a CIoT enhanced Node B (CIoT eNB) (not shown in FIG. 2G)communicatively coupled to the CIoT Access Network Gateway (CIoT GW)295. In certain examples, the RAN 288 can include multiple base stations(e.g., CIoT eNBs) connected to the CIoT GW 295, which can include MSC286, MME 284, SGSN 282, or S-GW 280. In certain examples, the internalarchitecture of RAN 288 and CIoT GW 295 may be left to theimplementation and need not be standardized.

As used herein, the term “circuitry” may refer to, be part of, orinclude an Application Specific Integrated Circuit (ASIC) or otherspecial purpose circuit, an electronic circuit, a processor (shared,dedicated, or group), or memory (shared, dedicated, or group) executingone or more software or firmware programs, a combinational logiccircuit, or other suitable hardware components that provide thedescribed functionality. In some aspects, the circuitry may beimplemented in, or functions associated with the circuitry may beimplemented by, one or more software or firmware modules. In someaspects, circuitry may include logic, at least partially operable inhardware. In some aspects, circuitry as well as modules disclosed hereinmay be implemented in combinations of hardware, software or firmware. Insome aspects, functionality associated with a circuitry can bedistributed across more than one piece of hardware or software/firmwaremodule. In some aspects, modules (as disclosed herein) may includelogic, at least partially operable in hardware. Aspects described hereinmay be implemented into a system using any suitably configured hardwareor software.

FIG. 2H illustrates an example Service Capability Exposure Function(SCEF) in accordance with some aspects. Referring to FIG. 2H, the SCEF272 can be configured to expose services and capabilities provided by3GPP network interfaces to external third party service provider servershosting various applications. In some aspects, a 3GPP network such asthe CIoT architecture 200G, can expose the following services andcapabilities: a home subscriber server (HSS) 256A, a policy and chargingrules function (PCRF) 256B, a packet flow description function (PFDF)256C a MME/SGSN 256D, a broadcast multicast service center (BM-SC) 256E,a serving call server control function (S-CSCF) 256F, a RAN congestionawareness function (RCAF) 256G, and one or more other network entities256H. The above-mentioned services and capabilities of a 3GPP networkcan communicate with the SCEF 272 via one or more interfaces asillustrated in FIG. 2H. The SCEF 272 can be configured to expose the3GPP network services and capabilities to one or more applicationsrunning on one or more service capability server (SCS)/applicationserver (AS), such as SCS/AS 254A, 254B, . . . , 254N. Each of the SCS/AG254A-254N can communicate with the SCEF 272 via application programminginterfaces (APIs) 252A, 252B, 252C, . . . , 252N, as seen in FIG. 2H.

FIG. 2I illustrates an example roaming architecture for SCEF (e.g., 272)in accordance with some aspects. Referring to FIG. 2I, the SCEF 272 canbe located in HPLMN 250 and can be configured to expose 3GPP networkservices and capabilities, such as 248, . . . , 246. In some aspects,3GPP network services and capabilities, such as 244, . . . , 242, can belocated within VPLMN 240. In this case, the 3GPP network services andcapabilities within the VPLMN 240 can be exposed to the SCEF 272 via aninterworking SCEF (IWK-SCEF) 297 within the VPLMN 240.

FIG. 2J illustrates an exemplary Next-Generation Radio Access Networkarchitecture, in accordance with some aspects. The 5GC 238, the NG-RAN236, and the gNBs 243J, in some aspects, may be similar or the same asthe 5GC 220, the NG-RAN 236, and the gNBs 243A/243B of FIG. 2B,respectively. In some aspects, network elements of the NG-RAN 236 may besplit into central and distributed units, and different central anddistributed units, or components of the central and distributed units,may be configured for performing different protocol functions. Forexample, different protocol functions of the protocol layers depicted inFIG. 4, FIG. 7, or FIG. 8.

In some aspects, the gNB 243J can comprise or be split into one or moreof a gNB Central Unit (gNB-CU) 234 and a gNB Distributed Unit (gNB-DU)232A/232B. Additionally, the gNB 243J can comprise or be split into oneor more of a gNB-CU-Control Plane (gNB-CU-CP) 230 and a gNB-CU-UserPlane (gNB-CU-UP) 228. The gNB-CU 234 is a logical node configured tohost the radio resource control layer (RRC), service data adaptationprotocol (SDAP) layer and packet data convergence protocol layer (PDCP)protocols of the gNB or RRC, and PDCP protocols of the E-UTRA-NR gNB(en-gNB) that controls the operation of one or more gNB-DUs. The gNB-DU232A/232B is a logical node configured to host the radio link controllayer (RLC), medium access control layer (MAC) and physical layer (PHY)layers of the gNB 243A/243B, 243J or en-gNB, and its operation is atleast partly controlled by gNB-CU 234. In some aspects, one gNB-DU232A/232B can support one or multiple cells.

The gNB-CU 234 comprises a gNB-CU-Control Plane (gNB-CU-CP) 230 and agNB-CU-User Plane (gNB-CU-UP) 228. The gNB-CU-CP 230 is a logical nodeconfigured to host the RRC and the control plane part of the PDCPprotocol of the gNB-CU 234 for an en-gNB or a gNB. The gNB-CU-UP 228 isa logical node configured to host the user plane part of the PDCPprotocol of the gNB-CU 234 for an en-gNB, and the user plane part of thePDCP protocol and the SDAP protocol of the gNB-CU 234 for a gNB.

The gNB-CU 234 and the gNB-DU 232A/232B can communicate via the F1interface and the gNB 243J can communicate with the gNB-CU via the Xn-Cinterface. The gNB-CU-CP 230 and the gNB-CU-UP 228 can communicate viathe E1 interface. Additionally, the gNB-CU-CP 230 and the gNB-DU232A/232B can communicate via the F1-C interface, and the gNB-DU232A/232B and the gNB-CU-UP 228 can communicate via the F1-U interface.

In some aspects, the gNB-CU 234 terminates the F1 interface connectedwith the gNB-DU 232A/232B, and in other aspects, the gNB-DU 232A/232Bterminates the F1 interface connected with the gNB-CU 234. In someaspects, the gNB-CU-CP 230 terminates the E1 interface connected withthe gNB-CU-UP 228 and the F1-C interface connected with the gNB-DU232A/232B. In some aspects, the gNB-CU-UP 228 terminates the E1interface connected with the gNB-CU-CP 230 and the F1-U interfaceconnected with the gNB-DU 232A/232B.

In some aspects, the F1 interface is a point-to-point interface betweenendpoints and supports the exchange of signalling information betweenendpoints and data transmission to the respective endpoints. The F1interface can support control plane and user plane separation andseparate the Radio Network Layer and the Transport Network Layer. Insome aspects, the E1 interface is a point-to-point interface between agNB-CU-CP 230 and a gNB-CU-UP 228 and supports the exchange ofsignalling information between endpoints. The E1 interface can separatethe Radio Network Layer and the Transport Network Layer, and in someaspects, the E1 interface may be a control interface not used for userdata forwarding.

Referring to the NG-RAN 236, the gNBs 243J of the NG-RAN 236 maycommunicate to the 5GC via the NG interfaces, and interconnected toother gNBs via the Xn interface. In some aspects, the gNBs 243J (e.g.,243A/243B) can be configured to support FDD mode, TDD mode or dual modeoperation. In certain aspects, for EN-DC, the S1-U interface and an X2interface (e.g., X2-C interface) for a gNB, consisting of a gNB-CU andgNB-DUs, can terminate in the gNB-CU.

FIG. 3A is a block diagram of an SDN architecture 300A, in accordancewith some aspects. The SDN architecture 300A can be implemented withinany of the systems shown in FIG. 1 or 2A-2J, and can be configured forSDN-based or NFV-based measurement and filtering operations and/orfiltering coefficient signalling methods described herein. The SDNarchitecture 300A comprises an application plane 302, a control plane304, and a data plane 306. The application plane 302 may include one ormore SDN applications (e.g., 303A, 303B, 303C), the SDN control plane304 can include a network controller (e.g., SDN controller 308), and theSDN data plane 306 can include one or more network elements 316A and316B. Some non-limiting examples of SDN applications 303A-303C caninclude software-defined mobile networking (SDMN), software-defined widearea network (SD-WAN), software-defined local area network (SD-LAN),network-related security applications, and distributed applications forgroup data delivery.

In some aspects, the SDN applications 303A-303C may be programs that candirectly communicate in a programmatic manner to the SDN controller 308,for example, to communicate network requirements and desired networkbehavior. The SDN applications 503A-C can communicate with the SDNcontroller 308 via a northbound interface (NBI) 310. The SDNapplications 503A-C can make decisions and determine operations, forexample, based on an abstracted view of a network. In some aspects, anSDN application 503A-C comprises SDN application logic 312 and one ormore NBI drivers 514.

The SDN controller 308 is a centralized logic entity that can coordinatecommunications and requested information from the SDN application plane302 to the SDN data plane 306. The SDN controller 308 can provide anabstracted view of the network to an SDN application 303, and thisabstracted view may include information describing certain networkevents as well as statistics. The SDN controller 308 may comprise an NBIagent 324, SDN control logic 326, and a control-data-plane interface(CDPI) driver 328. The SDN controller 308 may communicate with the oneor more network elements 316A-316B via the SDN CDPI 328. The SDN CDPI328 can enable capabilities advertisement, statistics reporting, eventnotification, and programmatic control of forwarding operations.

A network element, for example, can be device within the network, suchas a router, switch, RAN node, or a gateway. A network element 316 maycomprise an SDN data path 318, a logical device of a network thatincludes forwarding and data processing capabilities. The SDN data path318 can include an SDN CDPI agent 320, a forwarding engine 321, and aprocessing function 322, which can enable internal traffic processing orterminations for the network element 316 (e.g., SDN data path 318), andforwarding between external interfaces of the SDN data path 318. Incertain aspects, the forwarding engine 321 and processing function 322may be included in the SDN data path 318 as a set. The SDN data path 318may comprise combined physical resources, such as circuitry, and one ormore SDN data paths may be included within a single network element ordefined across multiple network elements.

FIG. 3B is a block diagram of an SDN architecture 300B, in accordancewith some aspects. The SDN architecture 300B can be implemented withinany of the systems shown in FIG. 1 or 2A-2J, and can be configured forSDN-based or NFV-based data measurement and filtering and/or filteringcoefficient configuration operations. In some aspects, the UE 330 (e.g.,UE 201/203) may communicate with a network (e.g., system 200A, system200B, system 200C) to access various IP services. In some aspects, thearchitecture of the network can be SDN-based and configured to include acontrol plane separated from user plane entities or functions (e.g.,network elements). A tunnel-less transmission can be used forprovisioning IP services for various devices to reduce messagingoverhead. The UE 330 can access the network via a RAN node 332. The RANnode 332 can communicate with a network controller 334 to request IPservices provisioning for the UE 330. In certain aspects, the networkcontroller 334 may be an SDN-based network controller. The networkcontroller 334 can communicate with a repository 336 (e.g., subscriptionrepository) to authenticate the UE 330, and the subscription repository336 can be configured to store (e.g., in memory) device and servicesubscription information (e.g., device and service subscriptioninformation for the UE 330).

In various aspects, the RAN node 332, the network controller 334, or acombination of the RAN node 332 and the network controller 334, canprovision a requested IP service (e.g., requested by the UE 330). IPservice provisioning can include allocating a group of IP addresses. Forexample, a pool of IPv4 addresses or an IPv6 prefix may be allocated fora requested IP service. In some aspects, a mobile network operator (MNO)can preconfigure the group of IP addresses. The preconfigured group ofIP addresses may be stored, for example, within memory of one or more ofthe subscription repository 336, the network controller 334, or the RANnode 332. If the RAN node 332 allocates the group of IP addresses, theRAN node 332 may request the group of IP addresses from the networkcontroller 334.

The network controller 334 can request the group of IP addresses fromthe subscription repository 336. A device, such as the RAN node 332,network controller 334, or a router can identify a requested IP serviceby a group of IP addresses (e.g., the allocated group of IP addresses)and can use an IP address of a packet to identify a received packet anddetermine a routing policy for forwarding the packet to an appropriatedata gateway (e.g., data gateway 338A, data gateway 338B, data gateway338C), router, or an endpoint (e.g., 104B).

The network controller 334 can also configure devices, such as one ormore data gateways (e.g., 338A, 338B, and 108) or routers (e.g., 106),for operations related to the requested IP service in a particularpacket data network (PDN). For example, the network controller 334 canconfigure such devices with routing tables (e.g., flow tables,forwarding tables) for implementing a routing policy. In some aspects,the routing policies may be based on information regarding the PDN. Aspart of the data gateway configuration, the network controller 334 mayprovide routing policies to the RAN node 332, the data gateways, or therouters (e.g., 106). In some aspects, if the RAN node 332 receives therouting policies, the RAN node 332 may provide the routing policies tothe data gateways.

In some aspects, the SDN architecture 300A can provide one or morenetwork elements as virtualized services, for example, a controller(e.g., SDN controller), router, switch, RAN node, gateway, or variousother network elements. These can be virtualized services of system 100or systems 200A and 200B.

In some aspects, virtualized network elements can be implemented indifferent planes of the SDN architecture 300A. For example, the SDNarchitecture 300A can include a router (e.g., virtualized router),switch (e.g., virtualized switch), or other virtualized network elementsthat are implemented in the data plane 306 of the SDN architecture 300A.The SDN architecture 300A can also include a controller (e.g., SDNcontroller), or other virtualized network elements that are implementedin the control plane 304 of the SDN architecture 300A.

In some aspects, the SDN architecture 300A, including the virtualizednetwork elements or services, can also provide virtualized networkfunctions. Network function virtualization (NFV) can facilitateprogrammability and flexibility of network functions, such as functionsperformed by virtualized network elements (e.g., routers, switches,controllers, etc.). In some aspects, such virtualized functions caninclude measurement and filtering and/or filtering coefficientconfiguration operations, as described herein.

In an SDN (e.g., SDN architecture 300A), virtualized network elements inthe control plane 304, such as the SDN controller, can maintain andconfigure a global state of the network. The virtualized networkelements (e.g., virtualized network functions) in the data plane 306,such as a virtualized router or switch (e.g., virtualized routerfunctionality or virtualized switching functionality), can operate as adata path configured for receiving data packets, identifying destinationaddresses for the data packets, and forwarding the data packetsaccording to the identified destination addresses. In some aspects, suchvirtualized network elements can identify the destination addresses byreferring to forwarding or routing tables that can include informationthat is structured according to routing policies and rules. Routingpolicies and rules may be established by network entities within thecontrol plane, for example, the SDN controller. An example of avirtualized function that can be performed within the SDN architecture300A or NFV system 1300 includes measurement and filtering and/orfiltering coefficient configuration operations.

FIG. 3C is a block diagram illustrating components, according to someexample aspects, of a system 300C to support NFV. The NFV system 300C,can include virtualized functions of the network entities of one or moreof systems 100 or the systems shown in FIGS. 2A-2J. In some aspects, theNFV system 300C can include virtualized functions of the SDN networkarchitecture of system 300A or 300B. Virtualized functions can includemeasurement and filtering operations and/or filtering coefficientsignalling methods described herein.

The system 300C is illustrated as including a virtualized infrastructuremanager (VIM) 340, a network function virtualization infrastructure(NFVI) 342, a VNF manager (VNFM) 344, virtualized network functions(VNFs) 346, an element manager (EM) 348, an NFV Orchestrator (NFVO) 350,and a network manager (NM) 352.

The VIM 340 manages the resources of the NFVI 342. The NFVI 342 caninclude physical or virtual resources and applications (e.g., includinghypervisors) used to execute the system 300C. The VIM 340 can manage thelife cycle of virtual resources with the NFVI 342 (e.g., creation,maintenance, and tear down of virtual machines (VMs) associated with oneor more physical resources), track VM instances, track performance,fault and security of VM instances and associated physical resources,and expose VM instances and associated physical resources to othermanagement systems. The VNFM 344 can manage the VNFs 346, and canconfigure and control network resources (e.g., in the SDN domain). TheVNFs 346 can be used to execute EPC or 5GC components/functions and RANcomponents/functions. The VNFM 344 can manage the life cycle of the VNFs346 and track performance, fault and security of the virtual aspects ofVNFs 346. The EM 348 can track the performance, fault and security ofthe functional aspects of VNFs 346. The tracking data from the VNFM 344and the EM 348 may comprise, for example, performance measurement (PM)data used by the VIM 340 or the NFVI 342. Both the VNFM 344 and the EM348 can scale up/down the quantity of VNFs of the system 300C.

The NFVO 350 can coordinate, authorize, release and engage resources ofthe NFVI 342 in order to provide the requested service (e.g., to executean EPC function, component, or slice). The NM 352 may provide a packageof end-user functions with the responsibility for the management of anetwork, which may include network elements with VNFs, non-virtualizednetwork functions, or both (management of the VNFs may occur via the EM348). In some aspects, the VNFM 344 can manage virtualized functions ofa network router or switch (e.g., router or switch 106A), and a networkcontroller (e.g., SDN controller 308, network controller 334). Incertain aspects, the virtualized router or switch functions can exist inthe data plane of the SDN domain (e.g., data plane 306 in SDNarchitecture 300A) and the controller functions can exist in the controlplane of the SDN domain (control plane 304 in SDN architecture 300A). Insome aspects, the VNFM 344 can manage virtualized measurement andfiltering operations and/or filtering coefficient signalling methods.

FIG. 4 illustrates protocol functions that may be implemented within orby devices of a network architecture, in accordance with some aspects.For example, such protocol functions may be implemented within wirelesscommunication devices such as UEs or BSs, and any other network entitiesconfigured for measurement and filtering operations and/or filteringcoefficient signalling methods. In some aspects, protocol layers mayinclude one or more of physical layer (PHY) 410, medium access controllayer (MAC) 420, radio link control layer (RLC) 430, packet dataconvergence protocol layer (PDCP) 440, service data adaptation protocol(SDAP) layer 447, radio resource control layer (RRC) 455, and non-accessstratum (NAS) layer 457, in addition to other higher layer functions notillustrated. In some aspects, the protocol layers may be implementedwithin or by any of the network components of FIGS. 2A-2J, such as thegNBs (e.g., 243A/243B, 243J), and various layers of the protocolfunctions may be implemented by one or more central or distributed unitsof the gNBs (e.g., gNB-CU 229J, gNB-DU 230J).

According to some aspects, protocol layers may include one or moreservice access points that may provide communication between two or moreprotocol layers. According to some aspects, PHY 410 may transmit andreceive physical layer signals 405 that may be received or transmittedrespectively by one or more other communication devices (e.g., UE 201,UE 201/203, device 500). According to some aspects, physical layersignals 405 may comprise one or more physical channels.

According to some aspects, an instance of PHY 410 may process requestsfrom and provide indications to an instance of MAC 420 via one or morephysical layer service access points (PHY-SAP) 415. According to someaspects, requests and indications communicated via PHY-SAP 415 maycomprise one or more transport channels. According to some aspects, aninstance of MAC 420 may process requests from and provide indications toan instance of RLC 430 via one or more medium access control serviceaccess points (MAC-SAP) 425. According to some aspects, requests andindications communicated via MAC-SAP 425 may comprise one or morelogical channels.

According to some aspects, an instance of RLC 430 may process requestsfrom and provide indications to an instance of PDCP 440 via one or moreradio link control service access points (RLC-SAP) 435. According tosome aspects, requests and indications communicated via RLC-SAP 435 maycomprise one or more RLC channels. According to some aspects, aninstance of PDCP 440 may process requests from and provide indicationsto one or more of an instance of RRC 455 and one or more instances ofSDAP 447 via one or more packet data convergence protocol service accesspoints (PDCP-SAP) 445. According to some aspects, requests andindications communicated via PDCP-SAP 445 may comprise one or more radiobearers.

According to some aspects, an instance of SDAP 447 may process requestsfrom and provide indications to one or more higher layer protocolentities via one or more service data adaptation protocol service accesspoints (SDAP-SAP) 449. According to some aspects, requests andindications communicated via SDAP-SAP 449 may comprise one or morequality of service (QoS) flows. According to some aspects, RRC entity455 may configure, via one or more management service access points(M-SAP) 450, aspects of one or more protocol layers, which may includeone or more instances of PHY 410, MAC 420, RLC 430, PDCP 440, and SDAP447. According to some aspects, an instance of RRC 455 may processrequests from and provide indications to one or more NAS 457 entitiesvia one or more RRC service access points (RRC-SAP) 456. According tosome aspects, a NAS entity 457 may process requests from and provideindications to one or more higher layer protocol entities via one ormore NAS service access points (NAS-SAP) 459.

FIG. 5 illustrates example components of a device 500 in accordance withsome aspects. For example, the device 500 may be a device configured formeasurement and filtering operations and/or filtering coefficientsignalling methods (e.g., UE 201, UE 203, UE 460, RAN Node 213/215). Insome aspects, the device 500 may include application circuitry 502,baseband circuitry 504, Radio Frequency (RF) circuitry 506, front-endmodule (FEM) circuitry 508, one or more antennas 510, and powermanagement circuitry (PMC) 512 coupled together at least as shown. Thecomponents of the illustrated device 500 may be included in a UE (e.g.,UE 201, UE 203, UE 460) or a RAN node (e.g., Macro RAN node 213, LP RANnode 215, gNB 480). In some aspects, the device 500 may include fewerelements (e.g., a RAN node may not utilize application circuitry 502,and instead may include a processor/controller to process IP datareceived from an EPC). In some aspects, the device 500 may includeadditional elements such as, for example, memory/storage, display,camera, sensor, or input/output (I/O) interface. In other aspects, thecomponents described below may be included in more than one device(e.g., said circuitries may be separately included in more than onedevice for Cloud-RAN (C-RAN) implementations).

The application circuitry 502 may include one or more applicationprocessors. For example, the application circuitry 502 may includecircuitry such as, but not limited to, one or more single-core ormulti-core processors. The processor(s) may include any combination ofgeneral-purpose processors and dedicated processors (e.g., graphicsprocessors, application processors, etc.). The processors may be coupledwith or may include memory/storage and may be configured to executeinstructions stored in the memory/storage to enable various applicationsor operating systems to run on the device 500. In some aspects,processors of application circuitry 502 may process IP data packetsreceived from an EPC.

The baseband circuitry 504 may include circuitry such as, but notlimited to, one or more single-core or multi-core processors. Thebaseband circuitry 504 may include one or more baseband processors orcontrol logic to process baseband signals received from a receive signalpath of the RF circuitry 506 and to generate baseband signals for atransmit signal path of the RF circuitry 506. Baseband processingcircuitry 504 may interface with the application circuitry 502 forgeneration and processing of the baseband signals and for controllingoperations of the RF circuitry 506. For example, in some aspects, thebaseband circuitry 504 may include a third generation (3G) basebandprocessor 504A, a fourth generation (4G) baseband processor 504B, afifth generation (5G) baseband processor 504C, or other basebandprocessor(s) 504D for other existing generations, generations indevelopment or to be developed in the future (e.g., second generation(2G), sixth generation (6G), etc.). The baseband circuitry 504 (e.g.,one or more of baseband processors 504A-D) may handle various radiocontrol functions that enable communication with one or more radionetworks via the RF circuitry 506.

In other aspects, some or all of the functionality of basebandprocessors 504A-D may be included in modules stored in the memory 504Gand executed via a Central Processing Unit (CPU) 504E. The radio controlfunctions may include, but are not limited to, signalmodulation/demodulation, encoding/decoding, radio frequency shifting,etc. In some aspects, modulation/demodulation circuitry of the basebandcircuitry 504 may include Fast-Fourier Transform (FFT), precoding, orconstellation mapping/demapping functionality. In some aspects,encoding/decoding circuitry of the baseband circuitry 504 may includeconvolution, tail-biting convolution, turbo, Viterbi, or Low-DensityParity Check (LDPC) encoder/decoder functionality. Aspects ofmodulation/demodulation and encoder/decoder functionality are notlimited to these examples and may include other suitable functionalityin other aspects.

In some aspects, the baseband circuitry 504 may include one or moreaudio digital signal processor(s) (DSP) 504F. The audio DSP(s) 504F maybe include elements for compression/decompression and echo cancellationand may include other suitable processing elements in other aspects.Components of the baseband circuitry may be suitably combined in asingle chip, a single chipset, or disposed on a same circuit board insome aspects. In some aspects, some or all of the constituent componentsof the baseband circuitry 504 and the application circuitry 502 may beimplemented together such as, for example, on a system on a chip (SOC).

In some aspects, the baseband circuitry 504 may provide forcommunication compatible with one or more radio technologies. Forexample, in some aspects, the baseband circuitry 504 may supportcommunication with an evolved universal terrestrial radio access network(EUTRAN) or other wireless metropolitan area networks (WMAN), a wirelesslocal area network (WLAN), a wireless personal area network (WPAN).Aspects in which the baseband circuitry 504 is configured to supportradio communications of more than one wireless protocol may be referredto as multi-mode baseband circuitry.

RF circuitry 506 may enable communication with wireless networks usingmodulated electromagnetic radiation through a non-solid medium. Invarious aspects, the RF circuitry 506 may include switches, filters,amplifiers, etc. to facilitate the communication with the wirelessnetwork. RF circuitry 506 may include a receive signal path which mayinclude circuitry to down-convert RF signals received from the FEMcircuitry 508 and provide baseband signals to the baseband circuitry504. RF circuitry 506 may also include a transmit signal path which mayinclude circuitry to up-convert baseband signals provided by thebaseband circuitry 504 and provide RF output signals to the FEMcircuitry 508 for transmission.

In some aspects, the receive signal path of the RF circuitry 506 mayinclude mixer circuitry 506A, amplifier circuitry 506B and filtercircuitry 506C. In some aspects, the transmit signal path of the RFcircuitry 506 may include filter circuitry 506C and mixer circuitry506A. RF circuitry 506 may also include synthesizer circuitry 506D forsynthesizing a frequency for use by the mixer circuitry 506A of thereceive signal path and the transmit signal path. In some aspects, themixer circuitry 506A of the receive signal path may be configured todown-convert RF signals received from the FEM circuitry 508 based on thesynthesized frequency provided by synthesizer circuitry 506D. Theamplifier circuitry 506B may be configured to amplify the down-convertedsignals and the filter circuitry 506C may be a low-pass filter (LPF) orband-pass filter (BPF) configured to remove unwanted signals from thedown-converted signals to generate output baseband signals. Outputbaseband signals may be provided to the baseband circuitry 504 forfurther processing. In some aspects, the output baseband signals may bezero-frequency baseband signals, although this is not a requirement. Insome aspects, mixer circuitry 506A of the receive signal path maycomprise passive mixers, although the scope of the aspects is notlimited in this respect.

In some aspects, the mixer circuitry 506A of the transmit signal pathmay be configured to up-convert input baseband signals based on thesynthesized frequency provided by the synthesizer circuitry 506D togenerate RF output signals for the FEM circuitry 508. The basebandsignals may be provided by the baseband circuitry 504 and may befiltered by filter circuitry 506C. In some aspects, the mixer circuitry506A of the receive signal path and the mixer circuitry 506A of thetransmit signal path may include two or more mixers and may be arrangedfor quadrature down-conversion and up-conversion, respectively. In someaspects, the mixer circuitry 506A of the receive signal path and themixer circuitry 506A of the transmit signal path may include two or moremixers and may be arranged for image rejection (e.g., Hartley imagerejection). In some aspects, the mixer circuitry 506A of the receivesignal path and the mixer circuitry 506A may be arranged for directdown-conversion and direct up-conversion, respectively. In some aspects,the mixer circuitry 506A of the receive signal path and the mixercircuitry 506A of the transmit signal path may be configured forsuper-heterodyne operation.

In some aspects, the output baseband signals and the input basebandsignals may be analog baseband signals, although the scope of theaspects is not limited in this respect. In some alternate aspects, theoutput baseband signals and the input baseband signals may be digitalbaseband signals. In these alternate aspects, the RF circuitry 506 mayinclude analog-to-digital converter (ADC) and digital-to-analogconverter (DAC) circuitry and the baseband circuitry 504 may include adigital baseband interface to communicate with the RF circuitry 506.

In some dual-mode aspects, a separate radio IC circuitry may be providedfor processing signals for each spectrum, although the scope of theaspects is not limited in this respect. In some aspects, the synthesizercircuitry 506D may be a fractional-N synthesizer or a fractional N/N+1synthesizer, although the scope of the aspects is not limited in thisrespect as other types of frequency synthesizers may be suitable. Forexample, synthesizer circuitry 506D may be a delta-sigma synthesizer, afrequency multiplier, or a synthesizer comprising a phase-locked loopwith a frequency divider. The synthesizer circuitry 506D may beconfigured to synthesize an output frequency for use by the mixercircuitry 506A of the RF circuitry 506 based on a frequency input and adivider control input. In some aspects, the synthesizer circuitry 506Dmay be a fractional N/N+1 synthesizer.

In some aspects, frequency input may be provided by a voltage-controlledoscillator (VCO), although that is not a requirement. Divider controlinput may be provided by either the baseband circuitry 504 or theapplications processor 502 depending on the desired output frequency. Insome aspects, a divider control input (e.g., N) may be determined from alook-up table based on a channel indicated by the applications processor502.

Synthesizer circuitry 506D of the RF circuitry 506 may include adivider, a delay-locked loop (DLL), a multiplexer and a phaseaccumulator. In some aspects, the divider may be a dual modulus divider(DMD) and the phase accumulator may be a digital phase accumulator(DPA). In some aspects, the DMD may be configured to divide the inputsignal by either N or N+1 (e.g., based on a carry out) to provide afractional division ratio. In some example aspects, the DLL may includea set of cascaded, tunable, delay elements, a phase detector, a chargepump and a D-type flip-flop. In these aspects, the delay elements may beconfigured to break a VCO period up into Nd equal packets of phase,where Nd is the number of delay elements in the delay line. In this way,the DLL provides negative feedback to help ensure that the total delaythrough the delay line is one VCO cycle.

In some aspects, synthesizer circuitry 506D may be configured togenerate a carrier frequency as the output frequency, while in otheraspects, the output frequency may be a multiple of the carrier frequency(e.g., twice the carrier frequency, four times the carrier frequency)and used in conjunction with quadrature generator and divider circuitryto generate multiple signals at the carrier frequency with multipledifferent phases with respect to each other. In some aspects, the outputfrequency may be a LO frequency (f_(LO)). In some aspects, the RFcircuitry 506 may include an IQ/polar converter.

FEM circuitry 508 may include a receive signal path which may includecircuitry configured to operate on RF signals received from one or moreantennas 510, amplify the received signals and provide the amplifiedversions of the received signals to the RF circuitry 506 for furtherprocessing. FEM circuitry 508 may also include a transmit signal pathwhich may include circuitry configured to amplify signals fortransmission provided by the RF circuitry 506 for transmission by one ormore of the one or more antennas 510. In various aspects, theamplification through the transmit or receive signal paths may be donesolely in the RF circuitry 506, solely in the FEM 508, or in both the RFcircuitry 506 and the FEM 508.

In some aspects, the FEM circuitry 508 may include a TX/RX switch toswitch between transmit mode and receive mode operation. The FEMcircuitry may include a receive signal path and a transmit signal path.The receive signal path of the FEM circuitry may include an LNA toamplify received RF signals and provide the amplified received RFsignals as an output (e.g., to the RF circuitry 506). The transmitsignal path of the FEM circuitry 508 may include a power amplifier (PA)to amplify input RF signals (e.g., provided by RF circuitry 506), andone or more filters to generate RF signals for subsequent transmission(e.g., by one or more of the one or more antennas 510).

In some aspects, the PMC 512 may manage power provided to the basebandcircuitry 504. In particular, the PMC 512 may control power-sourceselection, voltage scaling, battery charging, or DC-to-DC conversion.The PMC 512 may often be included when the device 500 is capable ofbeing powered by a battery, for example, when the device is included ina UE. The PMC 512 may increase the power conversion efficiency whileproviding desirable implementation size and heat dissipationcharacteristics.

While FIG. 5 shows the PMC 512 coupled only with the baseband circuitry504. However, in other aspects, the PMC 512 may be additionally oralternatively coupled with, and perform similar power managementoperations for, other components such as, but not limited to,application circuitry 502, RF circuitry 506, or FEM 508.

In some aspects, the PMC 512 may control, or otherwise be part of,various power saving mechanisms of the device 500. For example, if thedevice 500 is in an RRC_Connected state, where it is still connected tothe RAN node as it expects to receive traffic shortly, then it may entera state known as Discontinuous Reception Mode (DRX) after a period ofinactivity. During this state, the device 500 may power down for briefintervals of time and thus save power.

If there is no data traffic activity for an extended period of time,then the device 500 may transition off to an RRC_Idle state, where itdisconnects from the network and does not perform operations such aschannel quality feedback, handover, etc. The device 500 goes into a verylow power state and it performs paging where again it periodically wakesup to listen to the network and then powers down again. The device 500may not receive data in this state, in order to receive data, it musttransition back to RRC_Connected state. An additional power saving modemay allow a device to be unavailable to the network for periods longerthan a paging interval (ranging from seconds to a few hours). Duringthis time, the device is totally unreachable to the network and maypower down completely. Any data sent during this time incurs a largedelay and it is assumed the delay is acceptable.

Processors of the application circuitry 502 and processors of thebaseband circuitry 504 may be used to execute elements of one or moreinstances of a protocol stack (e.g., protocol stack described withrespect to FIG. 4, FIG. 7, or FIG. 8). For example, processors of thebaseband circuitry 504, alone or in combination, may be used executeLayer 3, Layer 2, or Layer 1 functionality, while processors of theapplication circuitry 502 may utilize data (e.g., packet data) receivedfrom these layers and further execute Layer 4 functionality (e.g.,transmission communication protocol (TCP) and user datagram protocol(UDP) layers). As referred to herein, Layer 3 may comprise a RRC layer(e.g., 455, 705). As referred to herein, Layer 2 may comprise a MAClayer (e.g., 420, 702), a RLC layer (e.g., 430, 703), and a PDCP layer(e.g., 440, 704). As referred to herein, Layer 1 may comprise a PHYlayer (e.g., 410, 701) of a UE/RAN node. Accordingly, in variousexamples, applicable means for transmitting may be embodied by suchdevices or media.

FIG. 6 illustrates example interfaces of baseband circuitry inaccordance with some aspects. As discussed above, the baseband circuitry504 of FIG. 5 may comprise processors 504A-504E and a memory 504Gutilized by said processors. Each of the processors 504A-504E mayinclude a memory interface, 604A-604E, respectively, to send/receivedata to/from the memory 504G.

The baseband circuitry 504 may further include one or more interfaces tocommunicatively couple to other circuitries/devices, such as a memoryinterface 612 (e.g., an interface to send/receive data to/from memoryexternal to the baseband circuitry 504), an application circuitryinterface 614 (e.g., an interface to send/receive data to/from theapplication circuitry 502 of FIG. 5), an RF circuitry interface 616(e.g., an interface to send/receive data to/from RF circuitry 506 ofFIG. 5), a wireless hardware connectivity interface 618 (e.g., aninterface to send/receive data to/from Near Field Communication (NFC)components, Bluetooth® components (e.g., Bluetooth® Low Energy), Wi-Fi®components, and other communication components), and a power managementinterface 620 (e.g., an interface to send/receive power or controlsignals to/from the PMC 512).

FIG. 7 is an illustration of a control plane protocol stack inaccordance with some aspects. In an aspect, a control plane 700 is shownas a communications protocol stack between the UE 201/203, the RAN node243 (or alternatively, the RAN node 245), and the AMF 247. The PHY layer701 may in some aspects transmit or receive information used by the MAClayer 702 over one or more air interfaces. The PHY layer 701 may furtherperform link adaptation or adaptive modulation and coding (AMC), powercontrol, cell search (e.g., for initial synchronization and handoverpurposes), and other measurements used by higher layers, such as the RRClayer 705. The PHY layer 701 may in some aspects still further performerror detection on the transport channels, forward error correction(FEC) coding/decoding of the transport channels, modulation/demodulationof physical channels, interleaving, rate matching, mapping onto physicalchannels, and Multiple Input Multiple Output (MIMO) antenna processing.

The MAC layer 702 may in some aspects perform mapping between logicalchannels and transport channels, multiplexing of MAC service data units(SDUs) from one or more logical channels onto transport blocks (TB) tobe delivered to PHY via transport channels, de-multiplexing MAC SDUs toone or more logical channels from transport blocks (TB) delivered fromthe PHY via transport channels, multiplexing MAC SDUs onto TBs,scheduling information reporting, error correction through hybridautomatic repeat request (HARD), and logical channel prioritization.

The RLC layer 703 may in some aspects operate in a plurality of modes ofoperation, including: Transparent Mode (TM), Unacknowledged Mode (UM),and Acknowledged Mode (AM). The RLC layer 703 may execute transfer ofupper layer protocol data units (PDUs), error correction throughautomatic repeat request (ARQ) for AM data transfers, and segmentationand reassembly of RLC SDUs for UM and AM data transfers. The RLC layer703 may also maintain sequence numbers independent of the ones in PDCPfor UM and AM data transfers. The RLC layer 703 may also in some aspectsexecute re-segmentation of RLC data PDUs for AM data transfers, detectduplicate data for AM data transfers, discard RLC SDUs for UM and AMdata transfers, detect protocol errors for AM data transfers, andperform RLC re-establishment.

The PDCP layer 704 may in some aspects execute header compression anddecompression of IP data, maintain PDCP Sequence Numbers (SNs), performin-sequence delivery of upper layer PDUs at re-establishment of lowerlayers, perform reordering and eliminate duplicates of lower layer SDUs,execute PDCP PDU routing for the case of split bearers, executeretransmission of lower layer SDUs, cipher and decipher control planeand user plane data, perform integrity protection and integrityverification of control plane and user plane data, control timer-baseddiscard of data, and perform security operations (e.g., ciphering,deciphering, integrity protection, integrity verification, etc.).

In some aspects, primary services and functions of the RRC layer 705 mayinclude broadcast of system information (e.g., included in MasterInformation Blocks (MIBs) or System Information Blocks (SIBs) related tothe non-access stratum (NAS)); broadcast of system information relatedto the access stratum (AS); paging initiated by 5GC 220 or NG-RAN239/236, establishment, maintenance, and release of an RRC connectionbetween the UE and NG-RAN (e.g., RRC connection paging, RRC connectionestablishment, RRC connection addition, RRC connection modification, andRRC connection release, also for carrier aggregation (CA) and DualConnectivity (DC) in NR or between E-UTRA and NR); establishment,configuration, maintenance, and release of Signalling Radio Bearers(SRBs) and Data Radio Bearers (DRBs); security functions including keymanagement, mobility functions including handover and context transfer,UE cell selection and reselection and control of cell selection andreselection, and inter-radio access technology (RAT) mobility; andmeasurement configuration for UE measurement reporting. The MIBs andSIBs may comprise one or more information elements (IEs), which may eachcomprise individual data fields or data structures. The RRC layer 705may also, in some aspects, execute QoS management functions, detectionof and recovery from radio link failure, and NAS message transferbetween the NAS 706 in the UE and the NAS 706 in the AMF 232.

In some aspects, the following NAS messages can be communicated duringthe corresponding NAS procedure, as illustrated in Table 1 below:

TABLE 1 5G NAS 5G NAS 4G NAS 4G NAS Message Procedure Message nameProcedure Registration Initial Attach Request Attach Requestregistration procedure procedure Registration Mobility Tracking AreaTracking area Request registration Update (TAU) updating update Requestprocedure procedure Registration Periodic TAU Request Periodic Requestregistration tracking area update updating procedure procedureDeregistration Deregistration Detach Detach Request procedure Requestprocedure Service Service request Service Service request Requestprocedure Request or procedure Extended Service Request PDU Session PDUsession PDN PDN Establishment establishment Connectivity connectivityRequest procedure Request procedure

In some aspects, when the same message is used for more than oneprocedure, then a parameter can be used (e.g., registration type or TAUtype) which indicates the specific purpose of the procedure, e.g.registration type=“initial registration”, “mobility registration update”or “periodic registration update”.

The UE 201 and the RAN node 243/245 may utilize an NG radio interface(e.g., an LTE-Uu interface or an NR radio interface) to exchange controlplane data via a protocol stack comprising the PHY layer 701, the MAClayer 702, the RLC layer 703, the PDCP layer 704, and the RRC layer 705.

The non-access stratum (NAS) protocols 706 form the highest stratum ofthe control plane between the UE 201 and the AMF 247 as illustrated inFIG. 7 In aspects, the NAS protocols 706 support the mobility of the UE201 and the session management procedures to establish and maintain IPconnectivity between the UE 201 and the UPF 249. In some aspects, the UEprotocol stack can include one or more upper layers, above the NAS layer706. For example, the upper layers can include an operating system layer724, a connection manager 720, and application layer 722. In someaspects, the application layer 722 can include one or more clients whichcan be used to perform various application functionalities, includingproviding an interface for and communicating with one or more outsidenetworks. In some aspects, the application layer 722 can include an IPmultimedia subsystem (IMS) client 726.

The NG Application Protocol (NG-AP) layer 715 may support the functionsof the N2 and N3 interface and comprise Elementary Procedures (EPs). AnEP is a unit of interaction between the RAN node 243/245 and the 5GC220. In certain aspects, the NG-AP layer 715 services may comprise twogroups: UE-associated services and non-UE-associated services. Theseservices perform functions including, but not limited to: UE contextmanagement, PDU session management and management of correspondingNG-RAN resources (e.g. Data Radio Bearers (DRBs)), UE capabilityindication, mobility, NAS signalling transport, and configurationtransfer (e.g. for the transfer of Self-Organizing Network (SON)information).

The Stream Control Transmission Protocol (SCTP) layer (which mayalternatively be referred to as the SCTP/IP layer) 714 may ensurereliable delivery of signalling messages between the RAN node 243/245and the AMF 247 based, in part, on the IP protocol, supported by the IPlayer 713. The L2 layer 712 and the L1 layer 711 may refer tocommunication links (e.g., wired or wireless) used by the RAN node243/245 and the AMF 247 to exchange information. The RAN node 243/245and the AMF 247 may utilize an N2 interface to exchange control planedata via a protocol stack comprising the L1 layer 711, the L2 layer 712,the IP layer 713, the SCTP layer 714, and the S1-AP layer 715.

FIG. 8 is an illustration of a user plane protocol stack in accordancewith some aspects. In this aspect, a user plane 800 is shown as acommunications protocol stack between the UE 201/203, the RAN node 243(or alternatively, the RAN node 245), and the UPF 249. The user plane800 may utilize at least some of the same protocol layers as the controlplane 700. For example, the UE 201/203 and the RAN node 243 may utilizean NR radio interface to exchange user plane data via a protocol stackcomprising the PHY layer 701, the MAC layer 702, the RLC layer 703, thePDCP layer 704, and the Service Data Adaptation Protocol (SDAP) layer716. The SDAP layer 716 may, in some aspects, execute a mapping betweena Quality of Service (QoS) flow and a data radio bearer (DRB) and amarking of both DL and UL packets with a QoS flow ID (QFI). In someaspects, an IP protocol stack 813 can be located above the SDAP 716. Auser datagram protocol (UDP)/transmission control protocol (TCP) stack820 can be located above the IP stack 813. A session initiation protocol(SIP) stack 822 can be located above the UDP/TCP stack 820, and can beused by the UE 201/203 and the UPF 249.

The General Packet Radio Service (GPRS) Tunneling Protocol for the userplane (GTP-U) layer 804 may be used for carrying user data within the 5Gcore network 220 and between the RAN (e.g., 210-J) and the 5G corenetwork 220. The user data transported can be packets in IPv4, IPv6, orPPP formats, for example. The UDP and IP security (UDP/IP) layer 803 mayprovide checksums for data integrity, port numbers for addressingdifferent functions at the source and destination, and encryption andauthentication on the selected data flows. The RAN node 243/245 and theUPF 249 may utilize an N3 interface to exchange user plane data via aprotocol stack comprising the L1 layer 911, the L2 layer 912, the UDP/IPlayer 803, and the GTP-U layer 804. As discussed above with respect toFIG. 6, NAS protocols support the mobility of the UE 201 and the sessionmanagement procedures to establish and maintain IP connectivity betweenthe UE 201 and the UPF 249.

FIG. 9 is a block diagram illustrating components, according to someexample aspects, able to read instructions from a machine-readable orcomputer-readable medium (e.g., a non-transitory machine-readablestorage medium) and perform any one or more of the methodologiesdiscussed herein, for example, measurement and filtering and/orfiltering coefficient configuration operations. Specifically, FIG. 9shows a diagrammatic representation of hardware resources 900 includingone or more processors (or processor cores) 910, one or morememory/storage devices 920, and one or more communication resources 930,each of which may be communicatively coupled via a bus 940. For aspectsin which node virtualization (e.g., NFV) is utilized, a hypervisor 902may be executed to provide an execution environment for one or morenetwork slices or sub-slices to utilize the hardware resources 900

The processors 910 (e.g., a central processing unit (CPU), a reducedinstruction set computing (RISC) processor, a complex instruction setcomputing (CISC) processor, a graphics processing unit (GPU), a digitalsignal processor (DSP) such as a baseband processor, an applicationspecific integrated circuit (ASIC), a radio-frequency integrated circuit(RFIC), another processor, or any suitable combination thereof) mayinclude, for example, a processor 912 and a processor 914.

The memory/storage devices 920 may include main memory, disk storage, orany suitable combination thereof. The memory/storage devices 920 mayinclude, but are not limited to, any type of volatile or non-volatilememory such as dynamic random-access memory (DRAM), static random-accessmemory (SRAM), erasable programmable read-only memory (EPROM),electrically erasable programmable read-only memory (EEPROM), Flashmemory, solid-state storage, etc.

The communication resources 930 may include interconnection or networkinterface components or other suitable devices to communicate with oneor more peripheral devices 904 or one or more databases 906 via anetwork 908. For example, the communication resources 930 may includewired communication components (e.g., for coupling via a UniversalSerial Bus (USB)), cellular communication components, NFC components,Bluetooth® components (e.g., Bluetooth® Low Energy), Wi-Fi® components,and other communication components.

Instructions 950 may comprise software, a program, an application, anapplet, an app, or other executable code for causing at least any of theprocessors 910 to perform any one or more of the methodologies discussedherein. The instructions 950 may reside, completely or partially, withinat least one of the processors 910 (e.g., within the processor's cachememory), the memory/storage devices 920, or any suitable combinationthereof. Furthermore, any portion of the instructions 950 may betransferred to the hardware resources 900 from any combination of theperipheral devices 904 or the databases 906. Accordingly, the memory ofprocessors 910, the memory/storage devices 920, the peripheral devices904, and the databases 906 are examples of computer-readable andmachine-readable media. Accordingly, in various examples, applicablemeans for storing may be embodied by such devices or media.

FIG. 10 illustrates a block diagram of an example machine 1000 uponwhich any one or more of the techniques (e.g., methodologies) discussedherein may be performed, for example, measurement and filtering and/orfiltering coefficient configuration operations. Examples, as describedherein, may include, or may operate by, logic or a number of components,or mechanisms in the machine 1000. Circuitry (e.g., processingcircuitry) is a collection of circuits implemented in tangible entitiesof the machine 1000 that include hardware (e.g., simple circuits, gates,logic, etc.). Circuitry membership may be flexible over time.Circuitries include members that may, alone or in combination, performspecified operations when operating. In an example, hardware of thecircuitry may be immutably designed to carry out a specific operation(e.g., hardwired). In an example, the hardware of the circuitry mayinclude variably connected physical components (e.g., execution units,transistors, simple circuits, etc.) including a machine readable mediumphysically modified (e.g., magnetically, electrically, moveableplacement of invariant massed particles, etc.) to encode instructions ofthe specific operation. In connecting the physical components, theunderlying electrical properties of a hardware constituent are changed,for example, from an insulator to a conductor or vice versa. Theinstructions enable embedded hardware (e.g., the execution units or aloading mechanism) to create members of the circuitry in hardware viathe variable connections to carry out portions of the specific operationwhen in operation. Accordingly, in an example, the machine readablemedium elements are part of the circuitry or are communicatively coupledto the other components of the circuitry when the device is operating.In an example, any of the physical components may be used in more thanone member of more than one circuitry. For example, under operation,execution units may be used in a first circuit of a first circuitry atone point in time and reused by a second circuit in the first circuitry,or by a third circuit in a second circuitry at a different time.Additional examples of these components with respect to the machine 1000follow. Accordingly, in various examples, applicable means forprocessing (e.g., receiving, decoding, updating, configuring,transmitting, modifying, etc.) may be embodied by such processingcircuitry.

In alternative aspects, the machine 1000 may operate as a standalonedevice or may be connected (e.g., networked) to other machines. In anetworked deployment, the machine 1000 may operate in the capacity of aserver machine, a client machine, or both in server-client networkenvironments. In an example, the machine 1000 may act as a peer machinein peer-to-peer (P2P) (or other distributed) network environment. Themachine 1000 may be a personal computer (PC), a tablet PC, a set-top box(STB), a personal digital assistant (PDA), a mobile telephone, a webappliance, a network router, switch or bridge, or any machine capable ofexecuting instructions (sequential or otherwise) that specify actions tobe taken by that machine. Further, while only a single machine isillustrated, the term “machine” shall also be taken to include anycollection of machines that individually or jointly execute a set (ormultiple sets) of instructions to perform any one or more of themethodologies discussed herein, such as cloud computing, software as aservice (SaaS), other computer cluster configurations.

The machine (e.g., computer system) 1000 may include a hardwareprocessor 1002 (e.g., a central processing unit (CPU), a graphicsprocessing unit (GPU), a hardware processor core, or any combinationthereof), a main memory 1004, a static memory (e.g., memory or storagefor firmware, microcode, a basic-input-output (BIOS), unified extensiblefirmware interface (UEFI), etc.) 1006, and mass storage 1008 (e.g., harddrive, tape drive, flash storage, or other block devices) some or all ofwhich may communicate with each other via an interlink (e.g., bus) 1030.The machine 1000 may further include a display unit 1010, analphanumeric input device 1012 (e.g., a keyboard), and a user interface(UI) navigation device 1014 (e.g., a mouse). In an example, the displayunit 1010, input device 1012 and UI navigation device 1014 may be atouch screen display. The machine 1000 may additionally include astorage device (e.g., drive unit) 1008, a signal generation device 1018(e.g., a speaker), a network interface device 1020, and one or moresensors 1016, such as a global positioning system (GPS) sensor, compass,accelerometer, or other sensor. The machine 1000 may include an outputcontroller 1028, such as a serial (e.g., universal serial bus (USB),parallel, or other wired or wireless (e.g., infrared (IR), near fieldcommunication (NFC), etc.) connection to communicate or control one ormore peripheral devices (e.g., a printer, card reader, etc.).

Registers of the processor 1002, the main memory 1004, the static memory1006, or the mass storage 1008 may be, or include, a machine readablemedium 1022 on which is stored one or more sets of data structures orinstructions 1024 (e.g., software) embodying or utilized by any one ormore of the techniques or functions described herein. The instructions1024 may also reside, completely or at least partially, within any ofregisters of the processor 1002, the main memory 1004, the static memory1006, or the mass storage 1008 during execution thereof by the machine1000. In an example, one or any combination of the hardware processor1002, the main memory 1004, the static memory 1006, or the mass storage1008 may constitute the machine readable media 1022. While the machinereadable medium 1022 is illustrated as a single medium, the term“machine readable medium” may include a single medium or multiple media(e.g., a centralized or distributed database, or associated caches andservers) configured to store the one or more instructions 1024.

The term “machine readable medium” may include any medium that iscapable of storing, encoding, or carrying instructions for execution bythe machine 1000 and that cause the machine 1000 to perform any one ormore of the techniques of the present disclosure, or that is capable ofstoring, encoding or carrying data structures used by or associated withsuch instructions. Non-limiting machine readable medium examples mayinclude solid-state memories, optical media, magnetic media, and signals(e.g., radio frequency signals, other photon-based signals, soundsignals, etc.). In an example, a non-transitory machine-readable mediumcomprises a machine readable medium with a plurality of particles havinginvariant (e.g., rest) mass, and thus are compositions of matter.Accordingly, non-transitory machine-readable media are machine readablemedia that do not include transitory propagating signals. Specificexamples of non-transitory machine readable media may include:non-volatile memory, such as semiconductor memory devices (e.g.,Electrically Programmable Read-Only Memory (EPROM), ElectricallyErasable Programmable Read-Only Memory (EEPROM)) and flash memorydevices; magnetic disks, such as internal hard disks and removabledisks; magneto-optical disks; and CD-ROM and DVD-ROM disks.

The instructions 1024 may be further transmitted or received over acommunications network 1026 using a transmission medium via the networkinterface device 1020 utilizing any one of a number of transferprotocols (e.g., frame relay, internet protocol (IP), transmissioncontrol protocol (TCP), user datagram protocol (UDP), hypertext transferprotocol (HTTP), etc.). Example communication networks may include alocal area network (LAN), a wide area network (WAN), a packet datanetwork (e.g., the Internet), mobile telephone networks (e.g., cellularnetworks), Plain Old Telephone (POTS) networks, and wireless datanetworks (e.g., Institute of Electrical and Electronics Engineers (IEEE)802.11 family of standards known as Wi-Fi®), IEEE 802.15.4 family ofstandards, peer-to-peer (P2P) networks, among others. In an example, thenetwork interface device 1020 may include one or more physical jacks(e.g., Ethernet, coaxial, or phone jacks) or one or more antennas toconnect to the communications network 1026. In an example, the networkinterface device 1020 may include a plurality of antennas to wirelesslycommunicate using at least one of single-input multiple-output (SIMO),multiple-input multiple-output (MIMO), or multiple-input single-output(MISO) techniques. The term “transmission medium” shall be taken toinclude any intangible medium that is capable of storing, encoding orcarrying instructions for execution by the machine 1000, and includesdigital or analog communications signals or other intangible medium tofacilitate communication of such software. A transmission medium is amachine readable medium.

FIG. 11 illustrates generally a flow of an exemplary method 1100 ofconfiguring filter coefficients, in accordance with some aspects. It isimportant to note that aspects of the method 1100 may include additionalor even fewer operations or processes in comparison to what isillustrated in FIG. 11. In addition, aspects of the method 1100 are notnecessarily limited to the chronological order that is shown in FIG. 11.In describing the method 1100, reference may be made to FIGS. 1-12,although it is understood that the method 1100 may be practiced with anyother suitable systems, interfaces and components. For example,reference may be made to systems 200A-200J described earlier forillustrative purposes, but the techniques and operations of the method1100 are not so limited. In some aspects, operations of the method 1100can be performed by a device (or an apparatus of the device) such as awireless communication device, UE, or any other network device asdescribed herein. Further, operations can be performed by virtualizedfunctions of the SDN or NFV networks described herein.

In operation 1102, a UE (e.g., UE 201 or 203) can decode, from RRCsignalling, a measurement configuration IE that includes a measurementquantity parameter, a RS-type filter configuration and at least onefilter coefficient. The measurement quantity parameter can indicate atleast one of a cell measurement quantity and a beam measurementquantity.

In operation 1104, the UE can filter (e.g., adapt a layer 3 filter toperforming filtering of) the at least one of the cell measurement resultand the beam measurement result, according to the measurementconfiguration IE. In some aspects, if the measurement quantity parameterindicates the cell measurement quantity, the UE (e.g., UE processingcircuitry) can adapt the layer 3 filter to perform filtering of the cellmeasurement result according to the RS type filter configuration and thefilter coefficient to determine a measurement evaluation input for ameasurement reporting operation. In some aspects, if the measurementquantity parameter indicates the beam measurement quantity, the UE canadapt the layer 3 filter to perform filtering of the beam measurementresult according to the RS type filter configuration and the filtercoefficient to determine a beam measurement selection input for a beammeasurement selection operation.

In operation 1106, the UE can encode a measurement report fortransmission to a BS (e.g., gNB, eNB). The measurement report caninclude at least one of measurement report information and beammeasurement selection information based on the measurement reportingoperation and the beam measurement selection operation. The UE memorycan be configured to store the measurement configuration IE. In someaspects, the measurement quantity parameter can include at least one ofa cell quantity coefficient or a beam quantity coefficient and the cellquantity coefficient can be a separate coefficient from the beamquantity coefficient.

The RS-type filter configuration can include at least one of a SSB-basedcoefficient or a CSI-RS-based coefficient and the SSB-based coefficientcan be a separate coefficient from the CSI-RS-based coefficient. Thefilter coefficient can be configured as a RSRP filter coefficient, anRSRQ filter coefficient or a RS-SINR filter coefficient, and the RSRPfilter coefficient, the RSRQ filter coefficient, and the RS-SINR filtercoefficient can be separate (e.g., layer 3) filtering coefficients.

FIG. 12 illustrates generally a flow of an exemplary method 1200 ofconfiguring filtering coefficients, in accordance with some aspects. Insome aspects, operations of the method 1200 can be performed by a device(or an apparatus of the device) such as a network entity, BS (e.g., gNB,eNB), or any other network device as described herein. Further,operations can be performed by virtualized functions of the SDN or NFVnetworks described herein.

In operation 1202, a BS can configure one or more filtering coefficientsand/or configurations. For example, the BS can configure an RS-typefilter configuration to include at least one of a SSB-based coefficientor a CSI-RS-based coefficient and the SSB-based coefficient can be aseparate coefficient from the CSI-RS-based coefficient. The BS can alsoconfigure at least one of a RSRP filter coefficient, a RSRQ filtercoefficient and a RS-SINR filter coefficient and the RSRP filtercoefficient, the RSRQ filter coefficient and the RS-SINR filtercoefficient can be separate layer 3 filtering coefficients. The BS canconfigure a measurement quantity parameter to include at least one of acell quantity coefficient or a beam quantity coefficient and the cellquantity coefficient can be a separate coefficient from the beamquantity coefficient. The BS can also configure a measurementconfiguration IE to include the RS-type filter configuration, themeasurement quantity parameter and at least one of the layer 3 filteringcoefficients.

In operation 1204, the BS can encode RRC signalling to include themeasurement configuration IE, for transmission to a UE, for determiningat least one of a measurement evaluation input for a measurementreporting operation or a beam measurement selection input for a beammeasurement selection operation. In operation 1206, the BS can decode,from signalling received from the UE, a measurement report including atleast one of measurement report information and beam measurementselection information, based on the measurement configuration IE. Insome aspects, the memory of the BS can be configured to store themeasurement report received from the UE.

Any of the radio links described herein may operate according to any oneor more of the following exemplary radio communication technologies orstandards including, but not limited to: a Global System for MobileCommunications (GSM) radio communication technology, a General PacketRadio Service (GPRS) radio communication technology, an Enhanced DataRates for GSM Evolution (EDGE) radio communication technology, or aThird Generation Partnership Project (3GPP) radio communicationtechnology, for example Universal Mobile Telecommunications System(UMTS), Freedom of Multimedia Access (FOMA), 3GPP Long Term Evolution(LTE), 3GPP Long Term Evolution Advanced (LTE Advanced), Code divisionmultiple access 2000 (CDMA2000), Cellular Digital Packet Data (CDPD),Mobitex, Third Generation (3G), Circuit Switched Data (CSD), High-SpeedCircuit-Switched Data (HSCSD), Universal Mobile TelecommunicationsSystem (Third Generation) (UMTS (3G)), Wideband Code Division MultipleAccess (Universal Mobile Telecommunications System) (W-CDMA (UMTS)),High Speed Packet Access (HSPA), High-Speed Downlink Packet Access(HSDPA), High-Speed Uplink Packet Access (HSUPA), High Speed PacketAccess Plus (HSPA+), Universal Mobile TelecommunicationsSystem-Time-Division Duplex (UMTS-TDD), Time Division-Code DivisionMultiple Access (TD-CDMA), Time Division-Synchronous Code DivisionMultiple Access (TD-CDMA), 3rd Generation Partnership Project Release 8(Pre-4th Generation) (3GPP Rel. 8 (Pre-4G)), 3GPP Rel. 9 (3rd GenerationPartnership Project Release 9), 3GPP Rel. 10 (3rd Generation PartnershipProject Release 10), 3GPP Rel. 11 (3rd Generation Partnership ProjectRelease 11), 3GPP Rel. 12 (3rd Generation Partnership Project Release12), 3GPP Rel. 13 (3rd Generation Partnership Project Release 13), 3GPPRel. 14 (3rd Generation Partnership Project Release 14), 3GPP Rel. 15(3rd Generation Partnership Project Release 15), 3GPP Rel. 16 (3rdGeneration Partnership Project Release 16), 3GPP Rel. 17 (3rd GenerationPartnership Project Release 17), 3GPP Rel. 18 (3rd GenerationPartnership Project Release 18), 3GPP 5G or 5G-NR, 3GPP LTE Extra,LTE-Advanced Pro, LTE Licensed-Assisted Access (LAA), MulteFire, UMTSTerrestrial Radio Access (UTRA), Evolved UMTS Terrestrial Radio Access(E-UTRA), Long Term Evolution Advanced (4th Generation) (LTE Advanced(4G)), cdmaOne (2G), Code division multiple access 2000 (Thirdgeneration) (CDMA2000 (3G)), Evolution-Data Optimized or Evolution-DataOnly (EV-DO), Advanced Mobile Phone System (1st Generation) (AMPS (1G)),Total Access Communication System/Extended Total Access CommunicationSystem (TACS/ETACS), Digital AMPS (2nd Generation) (D-AMPS (2G)),Push-to-talk (PTT), Mobile Telephone System (MTS), Improved MobileTelephone System (IMTS), Advanced Mobile Telephone System (AMTS), OLT(Norwegian for Offentlig Landmobil Telefoni, Public Land MobileTelephony), MTD (Swedish abbreviation for Mobiltelefonisystem D, orMobile telephony system D), Public Automated Land Mobile (Autotel/PALM),ARP (Finnish for Autoradiopuhelin, “car radio phone”), NMT (NordicMobile Telephony), High capacity version of NTT (Nippon Telegraph andTelephone) (Hicap), Cellular Digital Packet Data (CDPD), Mobitex,DataTAC, Integrated Digital Enhanced Network (iDEN), Personal DigitalCellular (PDC), Circuit Switched Data (CSD), Personal Handy-phone System(PHS), Wideband Integrated Digital Enhanced Network (WiDEN), iBurst,Unlicensed Mobile Access (UMA), also referred to as also referred to as3GPP Generic Access Network, or GAN standard), Zigbee, Bluetooth(r),Wireless Gigabit Alliance (WiGig) standard, mmWave standards in general(wireless systems operating at 10-300 GHz and above such as WiGig, IEEE802.11ad, IEEE 802.11ay, and the like), technologies operating above 300GHz and THz bands, (3GPP/LTE based or IEEE 802.11p and other),Vehicle-to-Vehicle (V2V), Vehicle-to-X (V2X), Vehicle-to-Infrastructure(V2I), and Infrastructure-to-Vehicle (I2V) communication technologies,3GPP cellular V2X, DSRC (Dedicated Short Range Communications)communication systems such as Intelligent-Transport-Systems and others.

Aspects described herein can be used in the context of any spectrummanagement scheme including, for example, dedicated licensed spectrum,unlicensed spectrum, (licensed) shared spectrum (such as Licensed SharedAccess (LSA) in 2.3-2.4 GHz, 3.4-3.6 GHz, 3.6-3.8 GHz and furtherfrequencies and Spectrum Access System (SAS) in 3.55-3.7 GHz and furtherfrequencies). Applicable exemplary spectrum bands include IMT(International Mobile Telecommunications) spectrum (including 450-470MHz, 790-960 MHz, 1710-2025 MHz, 2110-2200 MHz, 2300-2400 MHz, 2500-2690MHz, 698-790 MHz, 610-790 MHz, 3400 -3600 MHz, to name a few),IMT-advanced spectrum, IMT-2020 spectrum (expected to include 3600-3800MHz, 3.5 GHz bands, 700 MHz bands, bands within the 24.25-86 GHz range,for example), spectrum made available under the Federal CommunicationsCommission's “Spectrum Frontier” 5G initiative (including 27.5-28.35GHz, 29.1-29.25 GHz, 31-31.3 GHz, 37-38.6 GHz, 38.6-40 GHz, 42-42.5 GHz,57-64 GHz, 71-76 GHz, 81-86 GHz and 92 -94 GHz, etc.), the ITS(Intelligent Transport Systems) band of 5.9 GHz (typically 5.85-5.925GHz) and 63-64 GHz, bands currently allocated to WiGig such as WiGigBand 1 (57.24-59.40 GHz), WiGig Band 2 (59.40-61.56 GHz), WiGig Band 3(61.56-63.72 GHz), and WiGig Band 4 (63.72-65.88 GHz); the 70.2 GHz-71GHz band; any band between 65.88 GHz and 71 GHz; bands currentlyallocated to automotive radar applications such as 76-81 GHz; and futurebands including 94-300 GHz and above. Furthermore, the scheme can beused on a secondary basis on bands such as the TV White Space bands(typically below 790 MHz) where in particular the 400 MHz and 700 MHzbands can be employed. Besides cellular applications, specificapplications for vertical markets may be addressed, such as PMSE(Program Making and Special Events), medical, health, surgery,automotive, low-latency, drones, and the like.

Aspects described herein can also be applied to different Single Carrieror OFDM flavors (CP-OFDM, SC-FDMA, SC-OFDM, filter bank-basedmulticarrier (FBMC), OFDMA, etc.) and in particular 3GPP NR (New Radio)by allocating the OFDM carrier data bit vectors to the correspondingsymbol resources.

EXAMPLES

Although an aspect has been described with reference to specific exampleaspects, it will be evident that various modifications and changes maybe made to these aspects without departing from the broader spirit andscope of the present disclosure. Accordingly, the specification anddrawings are to be regarded in an illustrative rather than a restrictivesense. The accompanying drawings that form a part hereof show, by way ofillustration, and not of limitation, specific aspects in which thesubject matter may be practiced. The aspects illustrated are describedin sufficient detail to enable those skilled in the art to practice theteachings disclosed herein. Other aspects may be utilized and derivedtherefrom, such that structural and logical substitutions and changesmay be made without departing from the scope of this disclosure. ThisDetailed Description, therefore, is not to be taken in a limiting sense,and the scope of various aspects is defined only by the appended claims,along with the full range of equivalents to which such claims areentitled.

Such aspects of the inventive subject matter may be referred to herein,individually or collectively, by the term “aspect” merely forconvenience and without intending to voluntarily limit the scope of thisapplication to any single aspect or inventive concept if more than oneis in fact disclosed. Thus, although specific aspects have beenillustrated and described herein, it should be appreciated that anyarrangement calculated to achieve the same purpose may be substitutedfor the specific aspects shown. This disclosure is intended to cover anyand all adaptations or variations of various aspects. Combinations ofthe above aspects, and other aspects not specifically described herein,will be apparent to those of skill in the art upon reviewing the abovedescription.

In this document, the terms “a” or “an” are used, as is common in patentdocuments, to include one or more than one, independent of any otherinstances or usages of “at least one” or “one or more.” In thisdocument, the term “or” is used to refer to a nonexclusive or, such that“A or B” includes “A but not B,” “B but not A,” and “A and B,” unlessotherwise indicated. In this document, the terms “including” and “inwhich” are used as the plain-English equivalents of the respective terms“comprising” and “wherein.” Also, in the following claims, the terms“including” and “comprising” are open-ended, that is, a system, UE,article, composition, formulation, or process that includes elements inaddition to those listed after such a term in a claim are still deemedto fall within the scope of that claim. Moreover, in the followingclaims, the terms “first,” “second,” and “third,” etc. are used merelyas labels, and are not intended to impose numerical requirements ontheir objects.

The Abstract of the Disclosure is provided to allow the reader toquickly ascertain the nature of the technical disclosure. It issubmitted with the understanding that it will not be used to interpretor limit the scope or meaning of the claims. In addition, in theforegoing Detailed Description, it can be seen that various features aregrouped together in a single aspect for the purpose of streamlining thedisclosure. This method of disclosure is not to be interpreted asreflecting an intention that the claimed aspects require more featuresthan are expressly recited in each claim. Rather, as the followingclaims reflect, inventive subject matter lies in less than all featuresof a single disclosed aspect. Thus, the following claims are herebyincorporated into the Detailed Description, with each claim standing onits own as a separate aspect.

The following describes various examples of methods, machine-readablemedia, and systems (e.g., machines, devices, or other apparatus)discussed herein.

Example 1 is an apparatus of a user equipment (UE), the apparatuscomprising: memory; and processing circuitry configured to: decode, fromradio resource control (RRC) signaling, a measurement configurationinformation element (IE) including a measurement quantity parameter, areference signal (RS)-type filter configuration and at least one filtercoefficient, wherein the measurement quantity parameter indicates atleast one of a cell measurement quantity and a beam measurementquantity; adapt a layer 3 filter to filter the at least one of the cellmeasurement result and the beam measurement result, according to themeasurement configuration IE, wherein if the measurement quantityparameter indicates the cell measurement quantity, the processingcircuitry is configured to adapt the layer 3 filter to filter the cellmeasurement result according to the RS type filter configuration and thefilter coefficient to determine a measurement evaluation input for ameasurement reporting operation, and wherein if the measurement quantityparameter indicates the beam measurement quantity, the processingcircuitry is configured to adapt the layer 3 filter to filter the beammeasurement result according to the RS type filter configuration and thefilter coefficient to determine a beam measurement selection input for abeam measurement selection operation; and encode a measurement report,for transmission to a base station (BS), the measurement reportincluding at least one of measurement report information and beammeasurement selection information, based on the measurement reportingoperation and the beam measurement selection operation, and wherein thememory is configured to store the measurement configuration IE.

In Example 2, the subject matter of Example 1 includes, wherein themeasurement quantity parameter includes at least one of a cell quantitycoefficient or a beam quantity coefficient, and wherein the cellquantity coefficient is a separate coefficient from the beam quantitycoefficient.

In Example 3, the subject matter of Examples 1-2 includes, wherein theRS-type filter configuration includes at least one of a synchronizationsignal block (SSB)-based coefficient or a channel stateinformation-reference signal (CSI-RS)-based coefficient, and wherein theSSB-based coefficient is a separate coefficient from the CSI-RS-basedcoefficient.

In Example 4, the subject matter of Examples 1-3 includes, filteringcoefficients.

In Example 5, the subject matter of Examples 1-4 includes, wherein theprocessing circuitry is configured to: adapt transceiver circuitry toreceive at least one beam transmitted from the BS; determine a beammeasurement of the least one beam; adapt a layer 1 filter to filter thebeam measurement of the at least one beam to determine the beammeasurement result; and report the beam measurement result from thelayer 1 to the layer 3 for determining at least one of the measurementevaluation input and the beam measurement selection input.

In Example 6, the subject matter of Example 5 includes, wherein themeasurement configuration IE further includes at least one measurementobject coefficient of a measurement object, wherein the measurementobject coefficient is a separate coefficient from a second measurementobject coefficient of a second measurement object, and wherein theprocessing circuitry is configured to measure the at least one beam at afrequency indicated by the measurement object to determine at least oneof the cell measurement result or the beam measurement result.

In Example 7, the subject matter of Examples 5-6 includes, wherein themeasurement configuration IE further includes at least one measurementfrequency coefficient of a measurement frequency, wherein themeasurement frequency coefficient is a separate coefficient from asecond measurement frequency coefficient of a second measurementfrequency, and wherein the processing circuitry is configured to measurethe at least one beam at the measurement frequency indicated by themeasurement frequency coefficient to determine at least one of the cellmeasurement result or the beam measurement result.

In Example 8, the subject matter of Examples 5-7 includes, wherein thecell measurement result is a cell quality value and wherein theprocessing circuitry is configured to determine the cell quality valueby consolidating the beam measurement result.

In Example 9, the subject matter of Examples 2-8 includes, wherein themeasurement quantity parameter includes a single measurement quantitycoefficient for indicating the cell measurement quantity and the beammeasurement quantity.

In Example 10, the subject matter of Examples 3-9 includes, wherein theRS-type filter configuration includes a single RS-type filtercoefficient for indicating a SSB-based measurement and a CSI-RS-basedmeasurement.

In Example 11, the subject matter of Examples 4-10 includes, wherein thefilter coefficient is a single filter coefficient configured to indicatean RSRP-based measurement, an RSRQ-based measurement, and anRS-SINR-based measurement.

In Example 12, the subject matter of Examples 1-11 includes, wherein theprocessing circuitry is configured to evaluate reporting criteria usingthe measurement evaluation input to determine the measurement reportinformation.

In Example 13, the subject matter of Examples 11-12 includes, whereinthe processing circuitry is configured to select the beam measurementselection input to determine beam measurement information.

In Example 14, the subject matter of Examples 1-13 includes, wherein theapparatus further comprises a transceiver configured to be coupled to atleast one antenna, the antenna and the transceiver configured to receivethe RRC signaling and transmit the measurement report to the BS.

Example 15 is an apparatus of a base station (BS), the apparatuscomprising: memory; and processing circuitry adapted to: configure areference signal (RS)-type filter configuration to include, at least oneof a synchronization signal block (SSB)-based coefficient or a channelstate information-reference signal (CSI-RS)-based coefficient, whereinthe SSB-based coefficient is a separate coefficient from theCSI-RS-based coefficient; configure at least one of a reference signalreceived power (RSRP) filter coefficient, a reference signal receivedquality (RSRQ) filter coefficient and a reference signal-signal tointerference plus noise ratio (RS-SINR) filter coefficient, wherein theRSRP filter coefficient, the RSRQ filter coefficient, and the RS-SINRfilter coefficient are separate layer 3 filtering coefficients;configure a measurement quantity parameter to include at least one of acell quantity coefficient or a beam quantity coefficient, wherein thecell quantity coefficient is a separate coefficient from the beamquantity coefficient; configure a measurement configuration informationelement (IE) to include the RS-type filter configuration, themeasurement quantity parameter and at least one of the layer 3 filteringcoefficients; encode radio resource control (RRC) signaling to includethe measurement configuration IE, for transmission to a user equipment(UE), for determining at least one of a measurement evaluation input fora measurement reporting operation or a beam measurement selection inputfor a beam measurement selection operation; and decode, from signallingreceived from the UE, a measurement report including at least one ofmeasurement report information and beam measurement selectioninformation, based on the measurement configuration IE, and wherein thememory is configured to store the measurement report.

Example 16 is a computer-readable hardware storage device that storesinstructions for execution by one or more processors of a user equipment(UE), the instructions to configure the one or more processors to:decode, from radio resource control (RRC) signaling, a measurementconfiguration information element (IE) including a measurement quantityparameter, a reference signal (RS)-type filter configuration and atleast one filter coefficient, wherein the measurement quantity parameterindicates at least one of a cell measurement quantity and a beammeasurement quantity; adapt a layer 3 filter to filter the at least oneof the cell measurement result and the beam measurement result,according to the measurement configuration IE, wherein if themeasurement quantity parameter indicates the cell measurement quantity,the processing circuitry is configured to adapt the layer 3 filter tofilter the cell measurement result according to the RS type filterconfiguration and the filter coefficient to determine a measurementevaluation input for a measurement reporting operation, and wherein ifthe measurement quantity parameter indicates the beam measurementquantity, the processing circuitry is configured to adapt the layer 3filter to filter the beam measurement result according to the RS typefilter configuration and the filter coefficient to determine a beammeasurement selection input for a beam measurement selection operation;and encode a measurement report, for transmission to a base station(BS), the measurement report including at least one of measurementreport information and beam measurement selection information, based onthe measurement reporting operation and the beam measurement selectionoperation.

In Example 17, the subject matter of Example 16 includes, wherein themeasurement quantity parameter includes at least one of a cell quantitycoefficient or a beam quantity coefficient, and wherein the cellquantity coefficient is a separate coefficient from the beam quantitycoefficient.

In Example 18, the subject matter of Examples 16-17 includes, whereinthe RS-type filter configuration includes at least one of asynchronization signal block (SSB)-based coefficient or a channel stateinformation-reference signal (CSI-RS)-based coefficient, and wherein theSSB-based coefficient is a separate coefficient from the CSI-RS-basedcoefficient.

In Example 19, the subject matter of Examples 16-18 includes, filteringcoefficients.

In Example 20, the subject matter of Examples 16-19 includes, whereinthe instructions are to configure the one or more processors to: adapttransceiver circuitry to receive at least one beam transmitted from theBS; determine a beam measurement of the least one beam; adapt a layer 1filter to filter the beam measurement of the at least one beam todetermine the beam measurement result; and report the beam measurementresult from the layer 1 to the layer 3 for determining at least one ofthe measurement evaluation input and the beam measurement selectioninput.

Example 21 is a method of configuring filter coefficients comprising:decoding, from radio resource control (RRC) signaling, a measurementconfiguration information element (IE) including a measurement quantityparameter, a reference signal (RS)-type filter configuration and atleast one filter coefficient, wherein the measurement quantity parameterindicates at least one of a cell measurement quantity and a beammeasurement quantity; adapting a layer 3 filter to filter the at leastone of the cell measurement result and the beam measurement result,according to the measurement configuration IE, wherein if themeasurement quantity parameter indicates the cell measurement quantity,adapting the layer 3 filter to filter the cell measurement resultaccording to the RS type filter configuration and the filter coefficientto determine a measurement evaluation input for a measurement reportingoperation, and wherein if the measurement quantity parameter indicatesthe beam measurement quantity, adapting the layer 3 filter to filter thebeam measurement result according to the RS type filter configurationand the filter coefficient to determine a beam measurement selectioninput for a beam measurement selection operation; and encoding ameasurement report, for transmission to a base station (BS), themeasurement report including at least one of measurement reportinformation and beam measurement selection information, based on themeasurement reporting operation and the beam measurement selectionoperation.

In Example 22, the subject matter of Example 21 includes, wherein themeasurement quantity parameter includes at least one of a cell quantitycoefficient or a beam quantity coefficient, and wherein the cellquantity coefficient is a separate coefficient from the beam quantitycoefficient.

In Example 23, the subject matter of Examples 21-22 includes, whereinthe RS-type filter configuration includes at least one of asynchronization signal block (SSB)-based coefficient or a channel stateinformation-reference signal (CSI-RS)-based coefficient, and wherein theSSB-based coefficient is a separate coefficient from the CSI-RS-basedcoefficient.

In Example 24, the subject matter of Examples 21-23 includes, filteringcoefficients.

In Example 25, the subject matter of Examples 21-24 includes, adaptingtransceiver circuitry to receive at least one beam transmitted from theBS; determining a beam measurement of the least one beam; adapting alayer 1 filter to filter the beam measurement of the at least one beamto determine the beam measurement result; and reporting the beammeasurement result from the layer 1 to the layer 3 for determining atleast one of the measurement evaluation input and the beam measurementselection input.

In Example 26, the subject matter of Example 25 includes, wherein themeasurement configuration IE further includes at least one measurementobject coefficient of a measurement object, wherein the measurementobject coefficient is a separate coefficient from a second measurementobject coefficient of a second measurement object, and wherein thefurther comprises measuring the at least one beam at a frequencyindicated by the measurement object to determine at least one of thecell measurement result or the beam measurement result.

In Example 27, the subject matter of Examples 25-26 includes, whereinthe measurement configuration IE further includes at least onemeasurement frequency coefficient of a measurement frequency, whereinthe measurement frequency coefficient is a separate coefficient from asecond measurement frequency coefficient of a second measurementfrequency, and wherein the method further comprises measuring the atleast one beam at the measurement frequency indicated by the measurementfrequency coefficient to determine at least one of the cell measurementresult or the beam measurement result.

In Example 28, the subject matter of Examples 25-27 includes, whereinthe cell measurement result is a cell quality value and wherein themethod further comprises determining the cell quality value byconsolidating the beam measurement result.

In Example 29, the subject matter of Examples 22-28 includes, whereinthe measurement quantity parameter includes a single measurementquantity coefficient for indicating the cell measurement quantity andthe beam measurement quantity.

In Example 30, the subject matter of Examples 23-29 includes, whereinthe RS-type filter configuration includes a single RS-type filtercoefficient for indicating a SSB-based measurement and a CSI-RS-basedmeasurement.

In Example 31, the subject matter of Examples 24-30 includes, whereinthe filter coefficient is a single filter coefficient configured toindicate an RSRP-based measurement, an RSRQ-based measurement, and anRS-SINR-based measurement.

In Example 32, the subject matter of Example 31 includes, wherein themethod further comprises evaluating reporting criteria using themeasurement evaluation input to determine the measurement reportinformation.

In Example 33, the subject matter of Examples 31-32 includes, whereinthe method further comprises selecting the beam measurement selectioninput to determine beam measurement information.

Example 34 is a method of configuring filter coefficients comprising:configuring a reference signal (RS)-type filter configuration toinclude, at least one of a synchronization signal block (SSB)-basedcoefficient or a channel state information-reference signal(CSI-RS)-based coefficient, wherein the SSB-based coefficient is aseparate coefficient from the CSI-RS-based coefficient; configuring atleast one of a reference signal received power (RSRP) filtercoefficient, a reference signal received quality (RSRQ) filtercoefficient and a reference signal-signal to interference plus noiseratio (RS-SINR) filter coefficient, wherein the RSRP filter coefficient,the RSRQ filter coefficient, and the RS-SINR filter coefficient areseparate layer 3 filtering coefficients; configuring a measurementquantity parameter to include at least one of a cell quantitycoefficient or a beam quantity coefficient, wherein the cell quantitycoefficient is a separate coefficient from the beam quantitycoefficient; configuring a measurement configuration information element(IE) to include the RS-type filter configuration, the measurementquantity parameter and at least one of the layer 3 filteringcoefficients; encoding radio resource control (RRC) signaling to includethe measurement configuration IE, for transmission to a user equipment(UE), for determining at least one of a measurement evaluation input fora measurement reporting operation or a beam measurement selection inputfor a beam measurement selection operation; and decoding, fromsignalling received from the UE, a measurement report including at leastone of measurement report information and beam measurement selectioninformation, based on the measurement configuration IE.

Example 35 is at least one machine-readable medium includinginstructions that, when executed by processing circuitry, cause theprocessing circuitry to perform operations to implement of any ofExamples 1-34.

Example 36 is an apparatus comprising means to implement of any ofExamples 1-34.

Example 37 is a system to implement of any of Examples 1-34.

Example 38 is a method to implement of any of Examples 1-34.

In Example 39, the subject matter of Examples 1-38 includes, wherein theBS is a virtualized network function (VNF).

In Example 40, the subject matter of Examples 1-38 includes, wherein theBS is a function of a virtualized processing node of a network functionvirtualization (NFV) system.

Example 41 is at least one machine-readable medium includinginstructions that, when executed by processing circuitry, cause theprocessing circuitry to perform operations to implement of any ofExamples 1-40.

Example 42 is a software defined networking (SDN) system including oneor more virtualized functions adapted to perform any of the operationsof Examples 1 to 41.

Example 43 is a network function virtualization (NFV) system havingvirtualized processing nodes adapted to perform any of the operations ofExamples 1 to 42.

Example 44 is an Internet of Things (IoT) network topology, the IoTnetwork topology comprising respective communication links adapted toperform communications for the operations of any of Examples 1 to 43.

Example 45 is a network comprising respective devices and devicecommunication mediums for performing any of the operations of Examples 1to 44.

1. (canceled)
 2. An apparatus of a user equipment (UE), the apparatuscomprising: processor configured to cause the UE to: receiveradio-resource control (RRC) signaling comprising a measurementconfiguration, wherein the measurement configuration includes: separatemeasurement reference signal types for cell measurements and for beammeasurements, wherein the measurement reference signal types includechannel state information reference signals (CSI-RS) and synchronizationsignal block (SSB); separate sets of filtering coefficients for eachmeasurement reference signal type, wherein each set of filteringcoefficients includes separate layer 3 (L3) filtering coefficients for aplurality of measurement quantities, the plurality of measurementquantities including: reference signal received power (RSRP); referencesignal received quality (RSRQ); and reference signalsignal-and-interference-to-noise ratio (RS-SINR)); perform measurementsin accordance with the measurement configuration for measurementreporting; and transmit a measurement report based on the measurements.3. The apparatus of claim 2, wherein the processor is further configuredto cause the UE to perform L3 filtering on layer 1 (L1) beam measurementresults for one of the different RS types.
 4. The apparatus of claim 3,wherein to perform L3 filtering on the L1 beam measurement results forone of the different RS types is in response to an indication of a beammeasurement quantity.
 5. The apparatus of claim 3, wherein to perform L3filtering on the L1 beam measurement results for one of the different RStypes is in response to an indication of a cell measurement quantity. 6.The apparatus of claim 2, wherein the measurement configuration includesa reference signal type filter configuration.
 7. The apparatus of claim2, wherein the measurement configuration includes an indication tomeasure at least one beam at an indicated frequency.
 8. The apparatus ofclaim 2, wherein the processor comprises a baseband processor.
 9. A userequipment (UE), the UE comprising: a radio; and processor operablyconnected to the radio and configured to cause the UE to: receiveradio-resource control (RRC) signaling comprising a measurementconfiguration, wherein the measurement configuration includes: separatemeasurement reference signal types for at least one of cell measurementsand beam measurements; and separate sets of filtering coefficients forat least one measurement reference signal type, wherein each set offiltering coefficients includes separate layer 3 (L3) filteringcoefficients for each of one or more measurement quantities; performmeasurements in accordance with the measurement configuration formeasurement reporting; and transmit a measurement report based on themeasurements.
 10. The UE of claim 9, wherein the separate measurementreference signal types include channel state information referencesignals (CSI-RS) and synchronization signal block (SSB).
 11. The UE ofclaim 9, wherein the measurement quantities include reference signalreceived power (RSRP), reference signal received quality (RSRQ), andreference signal signal-and-interference-to-noise ratio (RS-SINR). 12.The UE of claim 9, wherein the processor is further configured to causethe UE to perform L3 filtering on layer 1 (L1) beam measurement resultsfor one of the different RS types.
 13. The UE of claim 12, wherein toperform L3 filtering on the L1 beam measurement results for one of thedifferent RS types is in response to an indication of a beam measurementquantity.
 14. The UE of claim 12, wherein to perform L3 filtering on theL1 beam measurement results for one of the different RS types is inresponse to an indication of a cell measurement quantity.
 15. The UE ofclaim 9, wherein the measurement configuration includes a referencesignal type filter configuration.
 16. The UE of claim 9, wherein themeasurement configuration includes an indication to measure at least onebeam at an indicated frequency.
 17. A method for operating a userequipment (UE), the method comprising: at the UE: receivingradio-resource control (RRC) signaling comprising a measurementconfiguration, wherein the measurement configuration includes: separatemeasurement reference signal types for at least one of cell measurementsand beam measurements; and separate sets of filtering coefficients forat least one measurement reference signal type, wherein each set offiltering coefficients includes separate layer 3 (L3) filteringcoefficients for each of one or more measurement quantities; performingmeasurements in accordance with the measurement configuration formeasurement reporting; and transmitting a measurement report based onthe measurements.
 18. The method of claim 17, wherein the separatemeasurement reference signal types include channel state informationreference signals (CSI-RS) and synchronization signal block (SSB). 19.The method of claim 17, wherein the measurement quantities includereference signal received power (RSRP), reference signal receivedquality (RSRQ), and reference signal signal-and-interference-to-noiseratio (RS-SINR).
 20. The method of claim 17, the method furthercomprising performing L3 filtering on layer 1 (L1) beam measurementresults for one of the different RS types.
 21. The method of claim 17,wherein the measurement configuration includes a reference signal typefilter configuration.